Re: GCC 3.3 template compile error?
Re: GCC 3.3 template compile error?
- Subject: Re: GCC 3.3 template compile error?
- From: Chris Hanson <email@hidden>
- Date: Mon, 15 Oct 2007 00:02:50 -0700
On Oct 14, 2007, at 9:08 AM, eric.bachard wrote:
Yes, you are right. Our problem is we don't use XCode for the build,
but only the terminal. Thus, we have to set everything, to simulate
XCode environment.
XCode does probably set some environment variables or something we
ignore. Afai see, at least one variable. All our tries ( we searched
a complete week) were unsuccessfull. We tested a lot of environment
variables: the build was ok, but not the rest (the appli did not work)
Did you ask for help here on the Xcode-users list or on the unix-
porting list? Please, don't spend a week banging your head against a
problem when you can ask those who have worked with the same
technologies extensively for help. Spreading the knowledge helps
everybody, and won't hurt your head as much. :)
There's a document on the Apple Developer Connection that will
probably help you immensely:
Porting UNIX/Linux Applications to Mac OS X
http://developer.apple.com/documentation/Porting/Conceptual/PortingUnix/index.html
It's part of an entire documentation section on porting:
Darwin Porting Reference Library
http://developer.apple.com/referencelibrary/Darwin/idxPorting-date.html#doclist
You'll specifically want to see the chapter in "Porting UNIX/Linux
Applications to Mac OS X" titled "Compiling Your Code in Mac OS X" -
it has details on how to compile for multiple CPU architectures,
passing the correct flags to the compiler and linker to tell them to
build against SDKs and for the appropriate CPU architectures.
This document also has cross-references to other guides which can tell
you more about how to do things like build the PowerPC and Intel
versions of your code independently (using separate SDKs or deployment
target settings) such that you can run on (say) Mac OS X 10.2.8 on
PowerPC hardware but Mac OS X 10.4 on Intel hardware, and still take
advantage of Mac OS X 10.3 or 10.4 features where available.
I'm not seeing the problem. You don't need to be running Panther
to target Panther.
Using XCode, I agree. Without, I'm not sure this is so easy with the
constraints OpenOffice.org does request for the build.
Constraints work in both directions. While I'm sure OpenOffice.org
does prescribe some of how their build process must work, so does Mac
OS X; if OpenOffice.org wants to build for Mac OS X (or attract more
developers to their Mac OS X port) they will need to accommodate how
Mac OS X works. That's just the nature of porting.
Just use the 10.3.9 SDK in /Developers/SDKs and compile on tiger
using gcc 4.0.1.
You can believe me, we tried : the build was perfect. But no way to
launch the application :-/
It should have just worked, assuming you were trying to run the built
application on Mac OS X 10.3.9 or later, as long as the SDK was passed
appropriately to both the compiler and the linker. See the pages
above for detailed information about how to do so.
-- Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden