|Re: LuaSocket [message #1085245 is a reply to message #1084923]
||Mon, 12 August 2013 16:47
| Marc Aubry
Registered: August 2012
It's a relevant use-case you figure-out, but not well cover by LDT for the moment.
I have open an enhancement about that to see what can be do to support this use-case nicely, see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=414889
Please comment the bug if you have an idea to how you imagine extending an execution environment in LDT.
But here, a quick help to solve your problem on LDT 1.0:
First, download the socket apifiles here:
Be careful, Theses files can be out-dated.
Then you need to put the apifiles in the build path, there are three ways to do that:
1) Just put the apifiles in the src folder
2) Manage an other source folder in your project to avoid polluting your code:
- create a new folder in your project
- copy the apifiles in it
- Add the folder to the buildpath, see : http://wiki.eclipse.org/Koneki/LDT/Developer_Area/User_Guides/User_Guide_1.0#Adding_source_folder
3) Extending an existing Execution Environment to add the apifiles. This is longer but you have to do only one time for all your projects.
- Download the appropriate EE from this list: http://wiki.eclipse.org/Koneki/LDT/User_Area/Available_Execution_Environments
- Open it using a archive manager
- Add apifiles to api.zip
- Rename the EE by ediding the .rockspec file.
- Re-zip the EE.
- Update your project EE, see http://wiki.eclipse.org/Koneki/LDT/Developer_Area/User_Guides/User_Guide_1.0#Managing_Execution_Environments
And thanks for asking
Powered by FUDForum
. Page generated in 0.10703 seconds