rev 3961 does NOT build on linux

[killerbot]

no rule to make target "envars_cdfdlg.lo" ==> makefile not correct

[afb]

Looks like a typo for "envvars_cfgdlg" ?

Code

Index: Makefile.am
===================================================================
--- Makefile.am	(revision 3961)
+++ Makefile.am	(arbetskopia)
@@ -11,9 +11,9 @@
 
 libenvvars_la_LIBADD = $(PLUGIN_WX_LIBS) ../../../sdk/libcodeblocks.la
 
-libenvvars_la_SOURCES = envvars.cpp envvars_cdfdlg.cpp envvars_common.cpp
+libenvvars_la_SOURCES = envvars.cpp envvars_cfgdlg.cpp envvars_common.cpp
 
-noinst_HEADERS = envvars.h envvars_cdfdlg.h envvars_common.h
+noinst_HEADERS = envvars.h envvars_cfgdlg.h envvars_common.h
 
 EXTRA_DIST = envvars.cbp envvars-unix.cbp envvars.xrc manifest.xml
 

Doesn't seem to build OK anyway, though:

Code

envvars_cfgdlg.cpp:36: error: 'XRCID' was not declared in this scope

[MortenMacFly]

I'm so sorry - I'm blind when it comes to linux. killerbot: Do you have the time to try to fix this? afb is right:
1.) the makefile is incorrect that way
2.) the XRCID issue should be fixed by adding <wx/xrc/xmlres.h> to the *.cpp file...
I don't have linux... sorry for that. :-(
With regards, Morten.

[afb]

I don't have linux... sorry for that. :-(

You would get the same problems in MSYS, no ?

[MortenMacFly]

I don't have linux... sorry for that. :-(

You would get the same problems in MSYS, no ?

...how to do? You mean compile the thing inside the MSYS console? Never tried that (sounds interesting though). If you mean the compiler only - then: No, it surely compiled fine. Otherwise I wouldn't have committed... ;-)
With regards, Morten.

[afb]

You would get the same problems in MSYS, no ?

...how to do? You mean compile the thing inside the MSYS console? Never tried that (sounds interesting though).

That is what I meant, yes. Sounded more like a Makefile/header problem, than a platform issue. (because I ran into the problem on Mac OS X, not Linux) Not sure if Code::Blocks supports MinGW/MSYS with configure yet (but it should). If it doesn't, you could also test with a virtual Linux without leaving Windows ? Also has the added bonus of testing wxGTK...

[MortenMacFly]

That is what I meant, yes. Sounded more like a Makefile/header problem, than a platform issue.

Alright! Will try that - I have indeed MSYS installed and configure *should* work - will report back.

If it doesn't, you could also test with a virtual Linux without leaving Windows ?

This would require me to have more processor power and HDD disk space. I had andLinux running but I had to remove it for the large software packages I require for work. :-( I should have burned it to CD though...

With regards, Morten.

[killerbot]

makefile.am fixed, that XRCID  : still looking into it. Note that the header you write to include was already included.

....

[MortenMacFly]

That is what I meant, yes. Sounded more like a Makefile/header problem, than a platform issue.

Alright! Will try that - I have indeed MSYS installed and configure *should* work - will report back.

Looks bad - compilation (setup) already fails at bootstrap phase with:

Code

./bootstrap: libtoolize: command not found

Looks like a job for google... ;-)
With regards, Morten.

Edit: Ok - this one was easy... I had mounted the wrong compiler path under MinGW (the one without extra tools like autotools etc...). But Now I receive:

Code

./bootstrap: /mingw/bin/aclocal: No such file or directory

...although it's there. I'm not sure if bootstrap will work with MinGW... Did anyone try?

[killerbot]

both fixed, builds again on non pch systems

[MortenMacFly]

both fixed, builds again on non pch systems

Nice! Thanks a lot. :-)

[Biplab]

...although it's there. I'm not sure if bootstrap will work with MinGW... Did anyone try?

AFAIR, I tried it once. But the compilation failed in MSYS. I posted that somewhere in forum. I was adviced to use project file.

Best Regards,

Biplab

[afb]

AFAIR, I tried it once. But the compilation failed in MSYS. I posted that somewhere in forum.

That's a bug, then. It shouldn't.

I was adviced to use project file.

That's a workaround, not a fix.

[Biplab]

That's a bug, then. It shouldn't.

Hmm.. Then I must try it again. BTW, couple of fixes were applied to the core during the bugfix week in April. So it could happen that the MSYS build was broken earlier.

[afb]

I'm not sure it has ever worked. Just saying that ultimately it should :-)