search

VirtualWorldsRepos / lslforge

Automatically exported from code.google.com/p/lslforge
0 stars 0 forks source link

Compiler doesn't recognize additions from 1.4 and 1.5 #35

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I recently updated LSL Forge to version 1.5, and it still can't understand 
OBJECT_ROOT, OBJECT_PHYSICS, or any other function you added in versions 1.4 
and 1.5

I attempted a clean install by purging LSLForge and re-downloading, but it had 
no effect. It's still broken.

I'm running the Windows version on Windows 8 Pro, in Eclipse 4.2.2

Original issue reported on code.google.com by brianpre...@gmail.com on 7 Jun 2013 at 4:41

GoogleCodeExporter commented 9 years ago 
I suspect LSLforge's installer is configured incorrectly, as its pieces are 
listed separately under Eclipse/Help/Installation Details/Installed Software. 
Every other kit is grouped together. i.e., C/C++ Development Tools and Eclipse 
SDK. But LSLforge has multiple entries, rather than a nested group.

Original comment by brianpre...@gmail.com on 7 Jun 2013 at 4:47

GoogleCodeExporter commented 9 years ago 
I noticed the executable path in the LSL Forge Perspective preference was 
wrongly pointing to version 0.1.3 in my installation.
It looks like 0.1.5 pulls in (at least for windows) 
Eclipse\plugins\lslforge_win32_x86_0.1.3 in addition to 
\lslforge_win32_x86_0.1.5, and points to it.
(I never installed 0.1.3 but found that path and setting on my machine anyway)
You can manually change the executable path in preferences, that should solve 
your issue. I have no clue why that is happening, I hope next release will be 
able to fix it

Original comment by firestar...@gmail.com on 31 Oct 2013 at 11:30

GoogleCodeExporter commented 9 years ago 
I expect you were just lucky, Firestar.  I dont' know where Eclipse is placing 
the 1.5 files, but it's not in the proper directory.  The only lslforge plugins 
in c:\Program Files\Eclipse\Plugins are from 1.3, installed 10 months ago. The 
new files are in limbo somewhere.

Original comment by brianpre...@gmail.com on 31 Oct 2013 at 7:51

GoogleCodeExporter commented 9 years ago 
Updating to 0.1.6, I were offered to update both packages (the LSLForge core 
and the platform-specific module). The setting in the LSLForge preferences were 
still pointing to the previous executable, so again I had to manually select 
the new one.
Brian, I suspect you might not have selected a platform-specific module, so you 
get updates only for the core. Try to reinstall it with "Install new 
software..." selecting the LSLForge site and look which optional modules are 
offered opening the LSLForge group. (I'm on Eclipse 4.3.1, but I don't think 
it's an Eclipse specific issue)

Original comment by firestar...@gmail.com on 6 Nov 2013 at 11:26

GoogleCodeExporter commented 9 years ago 
I'm afraid you are wrong. I selected core and Windows. Eclipse refused to
update either of them,  and left 1.4 in place. I tried deleting Forge, but
vthat also failed.

Clearly, Eclipse is hiding the old software somewhere other than Eclipse's
installation folder.

Original comment by brianpre...@gmail.com on 6 Nov 2013 at 3:48

GoogleCodeExporter commented 9 years ago 
Hi, sometimes the location is stored in the workspace's settings and override 
any defaults, even from a fresh install.  Please try installing a fresh version 
of eclipse and pointing it at a new workspace folder.  If this doesn't work, 
please reopen this ticket (or place a new one) and I'll try to help dig into 
the issue. - Newfie

Original comment by elnew...@gmail.com on 9 Nov 2013 at 11:09

GoogleCodeExporter commented 9 years ago

Original comment by elnew...@gmail.com on 9 Nov 2013 at 11:09