I thought that `make` was the simplest way to go. Now that I'm compiling for both Linux and OS X I see that this isn't the case. (Linux is the main target but testing on my MacBook is convenient, y'know)
There's a hundred thousand make-like things out there: Autoconf, cmake, qmake, scons, waf, rake, jake, etc. I want to invest time in learning one of these systems. Give me a few arguments as to why one is more suitable than the other please. Here are some criteria: - supports Linux, OS X (and preferably Windows) - supports cross-compiling - by "supports" I mean "was built with XYZ in mind" - I don't want a hundred thousand dependencies (i.e. the complete perl or python sdk) so I'm thinking scons and waf are out. - I don't care to use something simply because it's what everyone has done for the past 20 years - <unnamed popular "web langauge"> is a perfect example of why that's a terrible idea. AJ ONeal P.S. Just in case make-things are one of those vim vs emacs issues: 1) If you feel the urge to start a flamewar, please prefix it with "[OT] flamewar [was] ..." and continue the discussion that way. 2) And if you're not on the vim side, don't bother starting a flamewar. On Wed, Feb 2, 2011 at 11:59 AM, Michael Torrie <[email protected]> wrote: > On 02/02/2011 11:48 AM, AJ ONeal wrote: > > I'd like to have a makefile that works for both Linux and OS X which > > produces a *.so. > > Aren't OS X shared libraries .dylib? > > > It seems that in Linux I have to use -Wl as a prefix to -soname > > ${CC} -shared -Wl,-soname.... > > > > But on OS X I must omit the "-Wl" > > ${CC} -shared -soname... > > > > Any idea how I can make them both happy? > > This is the type of thing that libtool was sort of meant to solve, > albeit probably not as cleanly as it ought to be. > > If you use something like cmake or qmake, I'm sure what you need to do > is a lot easier than with a straight Makefile. > -------------------- > BYU Unix Users Group > http://uug.byu.edu/ > > The opinions expressed in this message are the responsibility of their > author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. > ___________________________________________________________________ > List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list >
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
