Latest version causing problems

Previous topic - Next topic

Crivens

You were right. The GLB lib was old and needed updating by using the trash option. Never even knew I needed it! Would it be a good idea to keep a record against each project of which GLB program lib was used with the compiled version? Then if a project is compiled against a newer version of the GLB program lib to do the trash option first before the actual compilation?

Cheers
Current fave quote: Cause you like musicians and I like people with boobs.

Kitty Hello

yes. It should always overwrite the lib.

Crivens

Really? Don't know why it didn't for me then. My macro should copy the libs directly from the project lib directory onto the Mac project. Nevermind, the clean option worked. Just must remember to use it everytime GLB is updated or the first time I compile it for that session (ie. I forgot I updated GLB yesterday and I haven't used this project since).

Cheers
Current fave quote: Cause you like musicians and I like people with boobs.

Kitty Hello

should = oughta, but doesn't, yet

Ian Price

Quote from: Kitty Hello on 2011-Oct-13
should = oughta, but doesn't, yet
HaHa! That's classic =D
I came. I saw. I played.