Menu
▾
▴
wxcode-users
|
From: sdfkjsjlh s. <sdf...@ya...> - 2010-05-25 22:15:42
|
Hi Francesco,
Today I tried generating the scripts on Ubuntu Karmic.
I re-ran bakefile_gen.
I then ran acregen.sh, which worked, so that's actually some progress. :-)
I then ran ../configure and I get the following:
checking for wxWidgets version >= 2.8.0... yes (version 2.8.10)
[: 411: 0: unexpected operator
[: 413: 0: unexpected operator
checking for wxWidgets static library... no
[: 411: 0: unexpected operator
[: 413: 0: unexpected operator
[: 411: 0: unexpected operator
[: 413: 0: unexpected operator
[: 411: 0: unexpected operator
[: 413: 0: unexpected operator
[: 411: 0: unexpected operator
[: 413: 0: unexpected operator
[: 411: 0: unexpected operator
[: 413: 0: unexpected operator
checking if wxWidgets was built with UNICODE enabled... yes
If 411 is a line number in the configure script, and I'm not certain that it is, that is the end of a sed command which I can't readily decode.
Running make also produces a bunch of
[: 411: 0: unexpected operator
[: 413: 0: unexpected operator
[: 411: 0: unexpected operator
[: 413: 0: unexpected operator
lines, followed by some compilation that fails, which is down to me, however it leads me to think that those numbers aren't lines in configure. Makefile has this many lines and 411 happens to be a lin that references a file that won't compile on Linux but removing the offending lines doesn't change the result.
Finally, a question. How do I arrange it so that the files that aren't Linux-compatible don't compile there? I can't see anything related in your guides.
Thanks.
|
|
From: Francesco <f18...@ya...> - 2010-06-08 21:09:49
|
Hi, sorry for the (huge) delay but I got time to boot on my Ubuntu only today :/ Anyway I tried regenerating the configure script and it worked fine... I took the freedom to commit to mmwx my changes and the (working) configure script I obtained. Said this, against my wxTRUNK (aka 2.9.1) mmwx doesn't build: /home/frm/work/wxCodeSVN/components/mmwx/bk-deps g++ -c -o mmwx_lib_mmDbase.o -I./include -I/usr/local/lib/wx/include/gtk2-unicode-static-2.9 -I/usr/local/include/wx-2.9 -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -pthread -O2 ./src/mmDbase.cpp In file included from ./src/mmDbase.cpp:11: ./include/wx/mmDbase.h:24:19: warning: wx/db.h: Nessun file o directory ./include/wx/mmDbase.h:25:24: warning: wx/dbtable.h: Nessun file o directory ./include/wx/mmDbase.h:30:22: warning: odbcinst.h: Nessun file o directory ... but this seems ok to me since contrib is gone in wx2.9... ;) Should you find other problems with regeneration of the configure script / the configure script itself, please let me know... HTH, Francesco 2010/5/26 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>: > > Hi Francesco, > > Today I tried generating the scripts on Ubuntu Karmic. > > I re-ran bakefile_gen. > I then ran acregen.sh, which worked, so that's actually some progress. :-) > I then ran ../configure and I get the following: > > checking for wxWidgets version >= 2.8.0... yes (version 2.8.10) > [: 411: 0: unexpected operator > [: 413: 0: unexpected operator > checking for wxWidgets static library... no > [: 411: 0: unexpected operator > [: 413: 0: unexpected operator > [: 411: 0: unexpected operator > [: 413: 0: unexpected operator > [: 411: 0: unexpected operator > [: 413: 0: unexpected operator > [: 411: 0: unexpected operator > [: 413: 0: unexpected operator > [: 411: 0: unexpected operator > [: 413: 0: unexpected operator > checking if wxWidgets was built with UNICODE enabled... yes > > If 411 is a line number in the configure script, and I'm not certain that it > is, that is the end of a sed command which I can't readily decode. > > Running make also produces a bunch of > > [: 411: 0: unexpected operator > [: 413: 0: unexpected operator > [: 411: 0: unexpected operator > [: 413: 0: unexpected operator > > lines, followed by some compilation that fails, which is down to me, however > it leads me to think that those numbers aren't lines in configure. Makefile > has this many lines and 411 happens to be a lin that references a file that > won't compile on Linux but removing the offending lines doesn't change the > result. > > Finally, a question. How do I arrange it so that the files that aren't > Linux-compatible don't compile there? I can't see anything related in your > guides. > > Thanks. > > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > wxCode-users mailing list > wxC...@li... > https://lists.sourceforge.net/lists/listinfo/wxcode-users > > |
|
From: sdfkjsjlh s. <sdf...@ya...> - 2010-06-10 16:29:32
|
Hi,
________________________________
From: Francesco <f18...@ya...>
To: wxc...@li...
Sent: Tue, June 8, 2010 4:09:40 PM
Subject: Re: [wxCode-users] Round we go...
Hi,
sorry for the (huge) delay but I got time to boot on my Ubuntu only today :/
-------------
No problem, I've been busy with other things myself.
Anyway I tried regenerating the configure script and it worked fine...
I took the freedom to commit to mmwx my changes and the (working)
configure script I obtained. Said this, against my wxTRUNK (aka 2.9.1)
mmwx doesn't build:
---------------
That's fine, thanks. I didn't expect it to build against 2.9, yet, as I haven't tried. I hope to get to 2.9 in the coming weeks and then I'll have a bunch of things to work on to get them running under it.
/home/frm/work/wxCodeSVN/components/mmwx/bk-deps g++ -c -o
mmwx_lib_mmDbase.o -I./include
-I/usr/local/lib/wx/include/gtk2-unicode-static-2.9
-I/usr/local/include/wx-2.9 -D_FILE_OFFSET_BITS=64 -D__WXGTK__
-pthread -O2 ./src/mmDbase.cpp
In file included from ./src/mmDbase.cpp:11:
./include/wx/mmDbase.h:24:19: warning: wx/db.h: Nessun file o
directory
./include/wx/mmDbase.h:25:24: warning: wx/dbtable.h: Nessun file o
directory
./include/wx/mmDbase.h:30:22: warning: odbcinst.h: Nessun file o
directory
...
but this seems ok to me since contrib is gone in wx2.9... ;)
-------------------
Yep. So...
>
> Finally, a question. How do I arrange it so that the files that aren't
> Linux-compatible don't compile there? I can't see anything related in your
> guides.
...is there any solution for this?
Thanks.
|
|
From: Francesco <f18...@ya...> - 2010-06-11 10:55:12
|
Hi Gary, 2010/6/10 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>: >> Finally, a question. How do I arrange it so that the files that aren't >> Linux-compatible don't compile there? I can't see anything related in your >> guides. > > ...is there any solution for this? well, I think the best way to address this issue is with a proper Readme.txt :) If you look at e.g. the template's readme.txt there are two sections "Installation - unix" and "Installation - win" which contain the commands to run for building the component under win or linux. I also think it should be quite straighforward for anyone experienced with cross-platform development to understand that the configure script is what needs to be run under linux and that the makefiles in the build folder are not meant for linux... ;) Francesco |
|
From: sdfkjsjlh s. <sdf...@ya...> - 2010-06-11 15:46:51
|
But that's the point. The build files are built from the same script so how do I tell the SCRIPT that it should include certain files in the Windows build files and not in the Unix ones? Thanks. ________________________________ From: Francesco <f18...@ya...> To: wxc...@li... Sent: Fri, June 11, 2010 5:55:06 AM Subject: Re: [wxCode-users] Round we go... Hi Gary, 2010/6/10 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>: >> Finally, a question. How do I arrange it so that the files that aren't >> Linux-compatible don't compile there? I can't see anything related in your >> guides. > > ...is there any solution for this? well, I think the best way to address this issue is with a proper Readme.txt :) If you look at e.g. the template's readme.txt there are two sections "Installation - unix" and "Installation - win" which contain the commands to run for building the component under win or linux. I also think it should be quite straighforward for anyone experienced with cross-platform development to understand that the configure script is what needs to be run under linux and that the makefiles in the build folder are not meant for linux... ;) Francesco ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ wxCode-users mailing list wxC...@li... https://lists.sourceforge.net/lists/listinfo/wxcode-users |
|
From: Francesco <f18...@ya...> - 2010-06-12 14:00:14
|
2010/6/11 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>: > > But that's the point. The build files are built from the same script so how > do I tell the SCRIPT that it should include certain files in the Windows > build files and not in the Unix ones? ah, ok, I didn't understand the question. What you need is something like: http://wxcode.svn.sourceforge.net/viewvc/wxcode/trunk/wxCode/components/extminiframe/build/wxextminiframe.bkl?revision=451&view=markup i.e. you define a variable conditionally (based on the value of WX_PORT) and then include that variable into a <sources> tag. Let me know if the ExtMiniFrame component's bakefile is not clear enough :) Francesco |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X