Hi
Can Carbide.c++ build a project with static libraries ?
I do have a project that compiles fine on command line and Codewarrior Pro that makes uses of several static libraries. When imported into Carbide.c++, the compilation goes OK but the link could not be completed. I got the following error in the carbide console:
Code:arm-none-symbianelf-ld.exe: C:\Symbian\9.1\S60_3rd_MR\epoc32\release\ARMV5\UREL\aacdeclib.lib C:\Symbian\9.1\S60_3rd_MR\epoc32\release\ARMV5\UREL\mpeg4declib.lib: No such file: No such file or directory
Just a little above, still in the console, the command which trigger the error is:
Code:'Invoking: GCCE Linker' arm-none-symbianelf-ld.exe --check-sections --no-undefined --no-allow-shlib-undefined -nostdlib -shared --entry _E32Startup -Tdata 0x400000 -Ttext 0x8000 --target1-abs --discard-locals --default-symver -u_E32Startup -L"C:\Program Files\CSL Arm Toolchain\arm-none-symbianelf\lib" -L"C:\Program Files\CSL Arm Toolchain\lib\gcc\arm-none-symbianelf\3.4.3" -soname "MyPlayer{000a0000}.exe" "C:\Symbian\9.1\S60_3rd_MR\EPOC32\RELEASE\ARMV5\UREL\eexe.lib" C:\Symbian\9.1\S60_3rd_MR\EPOC32\RELEASE\ARMV5\LIB\dfpaeabi.dso C:\Symbian\9.1\S60_3rd_MR\EPOC32\RELEASE\ARMV5\LIB\drtaeabi.dso C:\Symbian\9.1\S60_3rd_MR\EPOC32\RELEASE\ARMV5\LIB\dfprvct2_2.dso C:\Symbian\9.1\S60_3rd_MR\EPOC32\RELEASE\ARMV5\LIB\scppnwdl.dso C:\Symbian\9.1\S60_3rd_MR\EPOC32\RELEASE\ARMV5\LIB\drtrvct2_2.dso C:\Symbian\9.1\S60_3rd_MR\EPOC32\RELEASE\ARMV5\UREL\usrt2_2.lib -o "C:\Symbian\9.1\S60_3rd_MR\epoc32\release\GCCE\UDEB\MyPlayer.sym" -Map C:\Symbian\9.1\S60_3rd_MR\epoc32\release\GCCE\UDEB\\MyPlayer.exe.map ./src/MyPlayerApp.o ./src/MyPlayerAppDoc.o ./src/MyPlayerAppUi.o ./src/MyPlayerMainView.o ./src/MyPlayerVideoContainer.o ./src/MyPlayerSettingsContainer.o ./src/MyPlayerSettingsView.o ./src/nlcUtils.o ./src/nlcGfx.o ./src/nlcHttp.o "C:\Symbian\9.1\S60_3rd_MR\epoc32\release\ARMV5\UREL\aacdeclib.lib C:\Symbian\9.1\S60_3rd_MR\epoc32\release\ARMV5\UREL\mpeg4declib.lib" "C:\Symbian\9.1\S60_3rd_MR\epoc32\release\ARMV5\LIB\euser.dso" ......
The fact that aacdeclib.lib and mpeg4declib.lib are within the same "..." looks suspicious to me....



