CodeLite IDE

Posted: **Thu Oct 20, 2011 6:47 pm**

downloaded/installed codelite-3.0.0.5041-mingw4.4.1-wx2.9.2.exe

downloaded/extracted codelite-3.0.0.5041.tar.gz

opened command prompt

set path to c:\mingw-4.4.1\bin;%path%

started c:\program files (x86)\codelite\codelite.exe

opened c:\dev\codelite\\codelite-3.0.0.5041\LiteEditor.workspace

Attempted build

Codelite attempts to use 'make' rather than 'mingw32-make'

From 'Build Settings'/tab-'Build Systems' browsed for c:\mingw-4.4.1\bin\mingw32-make and selected, reflected in dialog field

OK'd out of dialogs, closed CodeLite, restarted.

CodeLite started with LiteEditor.workspace open

Attempted build again, but still attempting to use 'make', instead of mingw32-make.

What do I need to do to get this version of codelite to build itself? (And possibly anything else, I thought 'itself' was a good starting point.)

Thanks.

[EDIT]
(here's build log output)

Code: Select all

----------Build Started--------
MESSAGE: Entering directory `C:\dev\codelite\codelite-3.0.0.5041\'
C:\Windows\system32\cmd.exe /c "make -j 4"
----------Building project:[ LiteEditor - Unix_Make_J ]----------
MAKE Version 5.2  Copyright (c) 1987, 2000 Borland
Incorrect command line argument: -j

Syntax: MAKE [options ...] target[s]
    -B                Builds all targets regardless of dependency dates
    -Dsymbol[=string] Defines symbol [equal to string]
    -Idirectory       Names an include directory
    -K                Keeps (does not erase) temporary files created by MAKE
    -N                Increases MAKE's compatibility with NMAKE
    -Wfilename        Writes MAKE to filename updating all non-string options
    -Usymbol          Undefine symbol
    -ffilename        Uses filename as the MAKEFILE
    -a                Performs auto-dependency checks for include files
    -c                Caches auto-dependency information
    -e                Ignores redefinition of environment variable macros
    -i                Ignores errors returned by commands
    -l+               Enables use of long command lines
    -m                Displays the date and time stamp of each file
    -n                Prints commands but does not do them
    -p                Displays all macro definitions and implicit rules
    -q                Returns zero if target is up-to-date and nonzero
                      if it is not (for use in batch files)
    -r                Ignores rules and macros defined in BUILTINS.MAK
    -s                Silent, does not print commands before doing them
    -? or -h          Prints this message
      Options marked with '+' are on by default. To turn off a default
      option follow it by a '-', for example: -a-----------Build Ended----------
0 errors, 0 warnings

Posted: **Thu Oct 20, 2011 6:50 pm**

dlh wrote:set path to c:\mingw-4.4.1\bin;%path%

Not needed, if you installed MinGW provided by codelite, codelite does it for you

Please provide the build log

Eran

Posted: **Thu Oct 20, 2011 11:00 pm**

It is at the bottom of the original post. (I had added shortly after original post. Hmm, based on message timestamps, maybe not quick enough for you to see.)

Posted: **Thu Oct 20, 2011 11:06 pm**

You are building the wrong build configuration.

At the top of the 'Workspace' tab, make sure that you select WinReleaseUnicode and NOT 'Unix_Custom_Make'

Also, please use code tags for build logs etc - its easier to read ( I have edited your post)
Eran

Posted: **Thu Oct 20, 2011 11:07 pm**

You are building the wrong build configuration.

At the top of the 'Workspace' tab, make sure that you select WinReleaseUnicode and NOT 'Unix_Custom_Make'

Also, please use code tags for build logs etc - its easier to read ( I have edited your post)
Eran

Posted: **Fri Oct 21, 2011 4:09 pm**

OK, use code tags.

Selecting that build target addressed make issue, but still doesn't build, invalid argument '@<...>\PCH.txt', starting different thread.

Posted: **Fri Oct 21, 2011 4:11 pm**

Same as before: please post the complete build log

Eran

Posted: **Thu Nov 17, 2011 10:21 am**

I am having the same problem im trying to build a simple hello world.
but its not working here is the program:
------------------------------------------
#include <iostream>
using namespace std;

int main()
{
cout<<"hello world"<<endl;
return 0;
}
------------------------------------------
Here is the build:
----------Build Started--------
C:\Windows\system32\cmd.exe /c ""mingw32-make.exe" -j 2 -f "testing_wsp.mk""
'"mingw32-make.exe"' is not recognized as an internal or external command,
operable program or batch file.
----------Build Ended----------
0 errors, 0 warnings

Also
-------------------------------
Current working directory: C:\Users\Benson\Documents\c++\testing
Running program: le_exec.exe ./testing
Program exited with return code: 2686672
--------------------------------------------------

Downloaded version:codelite-3.0.0.5041.exe

Posted: **Thu Nov 17, 2011 3:59 pm**

benz0073 wrote:Downloaded version:codelite-3.0.0.5041.exe

You downloaded the IDE only, you should download the version that includes the compiler..

http://sourceforge.net/projects/codelit ... e/download

Eran

Posted: **Thu Nov 17, 2011 7:19 pm**

Thank for the quick reply, now it works

CodeLite IDE

win7, new install, build uses 'make' not 'mingw32-make'

win7, new install, build uses 'make' not 'mingw32-make'

Re: win7, new install, build uses 'make' not 'mingw32-make'

Re: win7, new install, build uses 'make' not 'mingw32-make'

Re: win7, new install, build uses 'make' not 'mingw32-make'

Re: win7, new install, build uses 'make' not 'mingw32-make'

Re: win7, new install, build uses 'make' not 'mingw32-make'

Re: win7, new install, build uses 'make' not 'mingw32-make'

Re: win7, new install, build uses 'make' not 'mingw32-make'

Re: win7, new install, build uses 'make' not 'mingw32-make'

Re: win7, new install, build uses 'make' not 'mingw32-make'