Page 1 of 1

attempt windows, build g++ complains

Posted: Fri Oct 21, 2011 4:14 pm
by dlh
(coming here from 'make' vs 'mingw32-make' problem...)

Attempting to build windows version from codelite-3.0.0.5041.tar.gz with installation of codelite-3.0.0.5041-mingw4.4.1-wx2.9.2.exe.

Appears g++ does not like '@' that is among arguments ('@"C:\dev\codelite\codelite-3.0.0.5041\PCH\PCH.txt"').

What else do I need to do?

Thanks.

build log:

Code: Select all

----------Build Started--------
C:\Windows\system32\cmd.exe /c ""C:/MinGW-4.4.1/bin/mingw32-make.exe"  -j 2 -f "LiteEditor_wsp.mk""
----------Building project:[ PCH - Release ]----------
mingw32-make[1]: Entering directory `C:/dev/codelite/codelite-3.0.0.5041/PCH'
g++ -c  precompiled_header_release.h -O2 -mthreads -DHAVE_W32API_H -D__WXMSW__ -DNDEBUG -D_UNICODE -IC:\wxWidgets-2.9.2\lib\gcc_dll\mswu -IC:\wxWidgets-2.9.2\include -DWXUSINGDLL -Wno-ctor-dtor-privacy -pipe -fmessage-length=0      -I. -I. 
mingw32-make[1]: Leaving directory `C:/dev/codelite/codelite-3.0.0.5041/PCH'
mingw32-make[1]: Entering directory `C:/dev/codelite/codelite-3.0.0.5041/PCH'
g++  -c  "C:/dev/codelite/codelite-3.0.0.5041/PCH/dummy.cpp" -O2 -mthreads -DHAVE_W32API_H -D__WXMSW__ -DNDEBUG -D_UNICODE -IC:\wxWidgets-2.9.2\lib\gcc_dll\mswu -IC:\wxWidgets-2.9.2\include -DWXUSINGDLL -Wno-ctor-dtor-privacy -pipe -fmessage-length=0      -o ./Release/dummy.o -I. -I. 
g++ -shared -fPIC -o ./Release/libPCH.a @"C:\dev\codelite\codelite-3.0.0.5041\PCH\PCH.txt" -L.   -O2  -mthreads -LC:\wxWidgets-2.9.2\lib\gcc_dll -lwxmsw29u -lwxtiff -lwxjpeg -lwxpng -lwxzlib -lwxregexu -lwxexpat -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwxregexu -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 
g++: @C:\dev\codelite\codelite-3.0.0.5041\PCH\PCH.txt: Invalid argument
mingw32-make[1]: *** [Release/libPCH.a] Error 1
mingw32-make[1]: Leaving directory `C:/dev/codelite/codelite-3.0.0.5041/PCH'
mingw32-make.exe: *** [All] Error 2
----------Build Ended----------
0 errors, 0 warnings

Re: attempt windows, build g++ complains

Posted: Fri Oct 21, 2011 4:53 pm
by eranif
I am not sure what is wrong your build configuration, but I suggest that you do this:
"Settings | Build Settings | Compilers | gnu g++ | Advanced"

and uncheck the option "Pass objects list to the linker via file"

Also, can you confirm that the executed gdb is the correct one? you can do this by:
Open any file inside codelite, Right click on the opened file tab header and from the context menu select 'Open Shell at file path...'

In the CMD.EXE that opened, type: 'which g++'
and paste the output here

Eran

Re: attempt windows, build g++ complains

Posted: Fri Oct 21, 2011 10:16 pm
by dlh
OK how do I set the base path to/for the settings/build-settings 'compilers' dialog tab gnu g++ executables branch?
(On build system tab, can browse for specific executable, but I don't see that for general compiler/link/etc tools... do I have to type all paths individually?)

probable problem:

Code: Select all

C:\dev\codelite\codelite-3.0.0.5041\CodeFormatter>which g++
C:/strawberry/c/bin/g++.EXE
That's from an installation of strawberry perl. I also have a 'normal' mingw install in addition to the codelite mingw-4.4.1, and sometimes a reactos build environment as well. I will also have cygwin eventually.

Re: attempt windows, build g++ complains

Posted: Fri Oct 21, 2011 10:45 pm
by eranif
in the compiler tools page (settings | build settings | compilers | gnu g++ | tools ) you have a field to set the PATH environment variable for this tools chain only.

For example:
Under Windows, set it like this:

Code: Select all

C:\MinGW-4.4.1\bin;$(PATH)
Eran

Re: attempt windows, build g++ complains

Posted: Tue Oct 25, 2011 7:17 pm
by dlh
OK...
1)I should have seen and understood the use of that field, sorry.

2)Appears the tooltip text needs an extra '\' (backslash) for the "C:\newpath" literal portion, i.e. "C:\\newpath".

Thanks for your help.