Hi Team! I’ve installed eclipse plug-in on neon and installed sdk today and followed all steps in the tutorial video, but when i open my context menu to export PCWLX nothing happend.. 
My toolpath under ..Preferences.. is set to the library.exe … any hints to solve this issue? Thanks Jan
hi Jan, its kind of hard to point into some direction, without any code or details regarding your installation. However. Please open you CPP (the one in src/programs/YOURPROGRAMNAME.CPP) in the editor (this is important, that it has focus, so not other files or xml files), and then try again to export your application agin, using right-click on the project tree. I assume your project does compile correctly, so either you have your binary in “Release” or “Debug” folder. Does that help?
Hey,
if just nothing happens this looks like the tool is not started at all.
Either something is wrong with the path or: If you are using a Linux OS make sure that the EngineeringLibraryBuilder has executable state.
You can add it with chmod +x EngineeringLibraryBuilder.exe. Also make sure that you have mono-complete or similar installed.
As this is a microsoft executable it will not function withoutIf it starts but nothing is exported then Vincents answer should solve your issue.
Hi Vincent, Hi Oliver unfortunatly it doesnt work… Its a win7 system, the EXE-file is at C:\\ and its ok (i tested with CMD-box). the focus is on my “src/programs” in the editor only the “Myprogram.cpp” is open. Right-click on the project tree showsup the export dialog but the edit field of “Library” says “no library found”. Under “Preferences- PLCnext” the tool path is set to "C:". I’ ve downloaded the EngineeringLibraryBuilder.exe again and replaced it – nothing happend. I checked the exe file for admin-rights with no better results. I’ve deleted my complete NEON installation and downloaded all packages again, followed the instructructions in the tut-video with same result: the export doesnt start… mmmh any docker container available?? Any ZIP-package of an complete NEON installation available? Thanks, Jan
Hi folks, problem solved: the path of the toolchain was much too long: here my original which doesnt work: D:\\PLCnext\\Win64_101\\Win64\\pxc-glibc-x86_64-axcf2152-image-mingw-cortexa9t2hf-neon-toolchain-2.2.1.tar\\pxc-glibc-x86_64-axcf2152-image-mingw-cortexa9t2hf-neon-toolchain-2.2.1\\sysroots ..and now i changed it to: D:\\PLCnext\\Win64_101\\Win64\\sysroots Wow.. that’s pretty nice to know - you should add it to the hints - or maybe its already in there? Greets Jan
Hey , good to hear that its working! _I think the problem is not the length of the path but the "n-toolchain-2.2.1.tar\\pxc-glib" part**.
** A dot “.tar” in a folder name might causes issues during compiling._ Edit:
I am wrong it actually was the path length.
The sign that is not allowed is a space " ". It is best to check the console in eclipse to see if everything compiles fine.
Usually a ***.so file gets created in the Release Folder.
That has to be there to get a working export
I am sure there was an error there…
Hi Oliver, yes- correct. Only when i change the path to the shorter version then Eclipse creates the binaries *.so and *.o - files in the Release or Debug folder. If the path length is too long, then you won’t get the binaries and the export doesnt start or shutted down in a sec because of no binaries. Start using it now - will see - greets Jan
Might be a Windows limitation, rather than a Phoenix Contact problem: https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx Maximum Path Length Limitation In the Windows API …, the maximum length for a path is MAX_PATH , which is defined as 260 characters. While Jan’s original path to the sysroots folder is under 200 chars, perhaps once the file names are added this might exceed MAX_PATH ? Another reason to ditch Windows for Linux. 