no rule to make target "envars_cdfdlg.lo" ==> makefile not correct
Looks like a typo for "envvars_cfgdlg" ?
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:
envvars_cfgdlg.cpp:36: error: 'XRCID' was not declared in this scope
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.
Quote from: MortenMacFly on May 14, 2007, 01:51:22 PM
I don't have linux... sorry for that. :-(
You would get the same problems in MSYS, no ?
Quote from: afb on May 14, 2007, 01:59:19 PM
Quote from: MortenMacFly on May 14, 2007, 01:51:22 PM
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.
Quote from: MortenMacFly on May 14, 2007, 02:03:24 PM
Quote from: afb on May 14, 2007, 01:59:19 PM
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...
Quote from: afb on May 14, 2007, 02:13:29 PM
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.
Quote from: afb on May 14, 2007, 02:13:29 PM
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.
makefile.am fixed, that XRCID : still looking into it. Note that the header you write to include was already included.
....
Quote from: MortenMacFly on May 14, 2007, 02:18:34 PM
Quote from: afb on May 14, 2007, 02:13:29 PM
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:
./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:
./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?
both fixed, builds again on non pch systems
Quote from: killerbot on May 14, 2007, 05:07:11 PM
both fixed, builds again on non pch systems
Nice! Thanks a lot. :-)
Quote from: MortenMacFly on May 14, 2007, 03:04:14 PM
...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
Quote from: Biplab on May 14, 2007, 05:56:13 PM
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.
QuoteI was adviced to use project file.
That's a workaround, not a fix.
Quote from: afb on May 14, 2007, 08:50:37 PM
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. :)
I'm not sure it has ever worked. Just saying that ultimately it should :-)