User forums > Help
Code::Blocks on MacOSX
afb:
--- Quote from: Takeshi Miya on October 27, 2006, 01:44:38 am ---What can we do to fix the Carbon-Intel bug?
--- End quote ---
Company has invested in an Intel mac, so I'll be hacking away at it in my spare time.
afb:
--- Quote from: bnilsson on October 27, 2006, 09:27:55 am ---This is the bootstrap I use on my Mac, working satisfactory for me.
It requires MacPort autotools.
--- End quote ---
You shouldn't need to hardcode the /opt/local prefix like that ?
Here is what I use for DarwinPorts:
--- Code: ---pre-configure {
reinplace "s|^libtoolize|glibtoolize|" \
"${worksrcpath}/bootstrap"
reinplace "s|aclocal$|aclocal -I ${prefix}/share/aclocal|" \
"${worksrcpath}/bootstrap"
}
configure.cmd ./bootstrap && ./configure
--- End code ---
For regular Mac OS X, all it needs is first searching for
the autoconf-2.57 and automake-1.7 and glibtool variants ?
(before falling back to just "autoconf", "automake", "libtool")
Making them variables is also a workable solution, as suggested:
http://developer.berlios.de/patch/?func=detailpatch&patch_id=1502&group_id=5358
bnilsson:
I am sure you are right, I just wanted to demostrate a working example, not necessarily a good example.
In case you haven't noticed, I am only an amateur c++ programmer, but a complete novice in shell scripts. :)
I will try your script and see if it is working for me too.
afb:
--- Quote from: bnilsson on October 27, 2006, 10:27:01 am ---I am sure you are right, I just wanted to demostrate a working example, not necessarily a good example.
In case you haven't noticed, I am only an amateur c++ programmer, but a complete novice in shell scripts. :)
I will try your script and see if it is working for me too.
--- End quote ---
I should note that the snippet was from the Portfile for MacPorts,
and thus it is written in tcl. Your bootstrap probably works fine,
but I'm looking for a solution that would work OK everywhere...
(i.e. there should be no need for the C::B user to tinker with it)
But if you are using MacPorts, those two "substitutions"
should be all you need to the regular bootstrap file from C::B ?
--- Code: ---s|^libtoolize|glibtoolize|
s|aclocal$|aclocal -I ${prefix}/share/aclocal|
--- End code ---
Sometimes I post the development solutions in the User forum,
sorry about that in advance, and do ask if anything is unclear...
afb:
To clarify, those substitions are to be made to the file itself -
they are not shell commands. s/foo/bar/ means to replace...
This might give some more info: http://en.wikipedia.org/wiki/Sed
But none of this should be needed, once "bootstrap" is fixed...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version