OSM Developer's Toolkit: LIB woes

Mortal Monkey on 8/9/2014 at 21:18

Hi folks, been a while.

I'm trying to get back into writing OSMs. Telliamed's toolkit appears to be a bit outdated; Visual Studio Express 2013 didn't manage to convert the included project files. I tried to configure things manually, but I may have screwed up somewhere.
The lg-d.lib compiles, but none of the IID names defined in iids.cpp are exported. I then get linker errors when I try to build the demo OSM. INITGUID is defined before the DEFINE_GUID() macros, as per MSDN's recommendation.
Any ideas?

On a related note, what's the status on (http://dromed.whoopdedo.org/lgscript/index) LgScript? Has anyone used it? I saw it listed in the Tutorials Overview, so I'm wondering how production ready it is.

LarryG on 9/9/2014 at 01:19

I asked Telliamed that same question, and the answer was LgScript is not ready for prime time. He said he uses it to quick prototype, but then writes the script as usual.

Telliamed on 9/9/2014 at 02:35

Install MinGW (using a package manager like (http://chocolatey.org/) Chocolatey to save a lot of typing) Or (http://codelite.org/) Codelite IDE includes GCC.

Install Git, from Chocolatey or (http://msysgit.github.io/) Git for Windows

Clone the repositories:

* (https://github.com/whoopdedo/lg)
* (https://github.com/whoopdedo/scriptlib)
* (https://github.com/whoopdedo/publicscripts) (optional)
* (https://github.com/whoopdedo/dh2) (really optional)

If you're building off of publicscripts, branch and erase the "Public", "T1", "T2" and "SS2" scripts so you're building just off of the skeleton.

Send pull requests when you make improvements.

Mortal Monkey on 9/9/2014 at 06:26

Thank you, I'll try that. A public repository is not a bad idea either, I should make one for my project.

Another question: I don't see an interface for particle systems. Any suggestions on how to hack it?

The Watcher on 9/9/2014 at 06:34

If you've like more features available to your scripts, you can also clone (https://github.com/TheWatcher/twscript) instead of publicscripts, that is clone:

(https://github.com/whoopdedo/lg)
(https://github.com/whoopdedo/scriptlib)
(https://github.com/TheWatcher/twscript)

twscript/base contains a base class, trap class, and trigger class that give you functionality much like NVscript, while twscript/twscript contains the scripts themselves.

Mortal Monkey on 9/9/2014 at 17:14

After doing mingw32-make in the /lg directory, I have a slightly more perplexing error:

Code:

C:\Users\FAXMAC~1\AppData\Local\Temp\ccqbOsbm.s:29: Error: no such instruction:
`xaddl eax,DWORD PTR [edx]'
Makefile:238: recipe for target 'refcnt.o' failed
mingw32-make: *** [refcnt.o] Error 1

The Watcher on 9/9/2014 at 20:07

... which version of gcc is that, I'm guessing a 3.x?

I'd really recommend using TDM-GCC+msys, you can find some (https://github.com/TheWatcher/twscript/blob/master/docs/Adapting_for_your_scripts.md#1-setting-up-the-compiler) setup instructions here. Section 5 and later of that doc are out of date and need fixing, but 1-4 should help you get going; that's essentially the setup I use.

Mortal Monkey on 9/9/2014 at 22:00

Why, it's the latest one, obviously. Unless...

Code:

C:\Projects\Dark\OSM\lg>where gcc
C:\lang\perl\c\bin\gcc.exe
C:\tools\MinGW\bin\gcc.exe

... yeah. Thanks!

LarryG on 9/9/2014 at 22:19

Wow. That appears clear and concise enough that I may dust off my "C++ for Ex-Fortran Programmers" book and give it a go. I never was able to understand how to set up the environment, and so never got started on writing scripts.

. . . The site you ref has GCC 4.8.1 OK to use that? 4.6.x seems depreciated.

Edit ... I spoke too soon. The instructions don't seem to apply to 4.8.1; in particular instruction 1.4 does not match up to the installer. I'll go back and try to find 4.6.1.

Edit ... there appear to be two 4.6.1 versions to choose, 4.6.1-tdm-1 SJLJ and 4.6.1-tdm-1 DW2, and I have no idea which is needed, or where to go from here as neither seems to have an installer.

Telliamed on 10/9/2014 at 03:34

You should be able to use 4.8.

Always use SJLJ. And 32-bit mode too. (Your toolset can be hosted on 64 bit, but should target 32)

~~And if you want to try something new, there's a (http://sourceforge.net/projects/msys2/) fork of MSys that seems to be more actively maintained.~~

Nevermind. That uses the DW2 build. (I'm not actually sure it won't work, just that I never tried.) Use (http://win-builds.org/) Winbuild instead.