hi,
i tried to compile shared lib after using static version without cleaning on Linux with CodeBlocks project file, i got linker errors.
The reason are wrong folder names for static versions on linux, they have the word shared within, so they mix with static object files.
So my request is to fix the project-file's static builds -> rename the object-folder-names to static, not shared.
thx
[fixed]Linker Errors due to wrong object-folder names in cbp
Re: Linker Errors due to wrong object-folder names in cb-pro
Just remembered this thread when I fixed some new problems in the c::b project files. So this is now also fixed in svn trunk r4723. Thanks for the report and sorry that I forgot about this for so long (and I know there's another thread about Makefile and c::b project file troubles on Win32 from Isomorphix ...).
IRC: #irrlicht on irc.libera.chat
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Re: [fixed]Linker Errors due to wrong object-folder names in
I just would like to mention something (not important):
To distinguish a static lib from a dynamic one (and compile them both without overwriting one), the naming convention could be changed:
static: libIrrlicht.a
dynamic: libIrrlicht.dll.a and Irrlicht.dll
Same with release and debug versions. For debug just add a 'd' ( => "...Irrlichtd..." ).
A "speciality" for MinGW: you can just link with the dll, you don't need the corresponding "import" library as with Visual Studio (don't know if this is a good practise, but it seems to work).
This way you just could say "build all" and you have all versions updated.
The downside of this method is, that for further different compile options (e.g. fast-math) you would need more suffixes (e.g. "f" or "fm") and so on.
To distinguish a static lib from a dynamic one (and compile them both without overwriting one), the naming convention could be changed:
static: libIrrlicht.a
dynamic: libIrrlicht.dll.a and Irrlicht.dll
Same with release and debug versions. For debug just add a 'd' ( => "...Irrlichtd..." ).
A "speciality" for MinGW: you can just link with the dll, you don't need the corresponding "import" library as with Visual Studio (don't know if this is a good practise, but it seems to work).
This way you just could say "build all" and you have all versions updated.
The downside of this method is, that for further different compile options (e.g. fast-math) you would need more suffixes (e.g. "f" or "fm") and so on.
Re: [fixed]Linker Errors due to wrong object-folder names in
Yeah, I know that naming scheme. It has pro's can contra's. The main disadvantage is that you can no longer replace the lib without rebuilding the applications using it. That's something I need right now far more often with Irrlicht than having several versions parallel (why would you want that ever really? Your app can only link to one anyway).
We can think about it again once we finally switch to CMake (well mostly - unfortunately CMake still produces no good project files for our favorite IDE so .cbp might even stay around).
We can think about it again once we finally switch to CMake (well mostly - unfortunately CMake still produces no good project files for our favorite IDE so .cbp might even stay around).
IRC: #irrlicht on irc.libera.chat
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm