On Thu, Jul 9, 2009 at 11:48 PM, Kenneth Riddile wrote:
> I am specifying it like this:
> set(CMAKE_OSX_ROOT iphoneos2.1)
Is that cut-and-pasted? The stack overflow page says it's
CMAKE_OSX_SYSROOT not CMAKE_OSX_ROOT ...
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X
se DYLD_FALLBACK_LIBRARY_PATH
instead... But install_name_tool is better.
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X development
Blog: http://www.raccoonfink.com/
Music: http://music.raccoonfink.com/
___
CMake mailing list
CMake@cmake.org
tch looks good to me, it's nice to have some more control over
what happens in the app bundles.
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X development
http://www.raccoonfink.com/
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
dered
harmful except for very specific uses. You're best off at least
setting it as DYLD_FALLBACK_LIBRARY_PATH (which behaves more like
you'd expect from LD_LIBRARY_PATH on other *NIXes) or, at least,
having the option to do so.
Other than that, this looks very cool.
--
Benjamin Reed
make* bits works fine, however. Perhaps the script
just needs to do a bit more cleaning first, to upgrade over old
versions?
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X development
http://www.racoonfink.com/
___
CMake mailing list
On Feb 13, 2008 5:26 PM, Pau Garcia i Quiles <[EMAIL PROTECTED]> wrote:
> Use ADD_CUSTOM_COMMAND.
Aha! Thanks...
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X development
http://www.racoonfink.com/
___
CMake mailing l
had to add my own targets to generate class files from
java files, and to generate the JNI .h file from the java. I suspect
the problem is there, but I'm not sure what.
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X development
http://www
ill for a javac and javah call...
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X development
http://www.racoonfink.com/
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
I think it should work,
although in an ideal world you'd put it in the library instead of the
binary so you wouldn't have to.
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X development
http://www.racoonfink.com/
___
CMake mailing list
CMak
ink time, between any of
the things you're linking.
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X development
http://www.racoonfink.com/
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
hese types of errors before if you're mixing and matching
g++'s (ie, your Qt was built with g++-3.3, but you're compiling using
g++-4.0, or vice-versa).
Not saying that's the problem, but it could be it...
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE,
On Jan 13, 2008 9:38 AM, Benjamin Reed <[EMAIL PROTECTED]> wrote:
> Since upgrading (from 2.4.6 I believe) to the RCs, all .app-bundles
> are referencing the build-dir versions of libraries, rather than their
> final rpath:
false alarm, it looks like this is what broke it:
http:/
y version 7.0.0,
current version 7.4.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0,
current version 1.0.0)
Is this some kind of relink issue? It only seems to happen for
programs, not for libraries...
--
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X
On 10/31/07, James Bigler <[EMAIL PROTECTED]> wrote:
> # -- Determine the version of OSX
> # -- 8 and less are OSX 10.0 - 10.4
> # -- 9 is 10.5 (LEOPARD)
> IF (APPLE)
>EXEC_PROGRAM(uname ARGS -v OUTPUT_VARIABLE DARWIN_VERSION)
you can also parse the output of /usr/bin/sw_vers, which will giv
On 9/11/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
Hrm. I wanted to say that CMake should treat a Universal binary as
multiple targets. But if gcc treats them as a single target, that's not
possible. Sticky wicket. Suppress Endian checks on MacOS X?
Basically. Although you'll sti
On 9/11/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
You'd have to trace through everything to see what's ultimately used. I
didn't mean, "Endianness checks in CMake are implemented directly with
TRY_RUN." Nor indirectly; I have no idea. I meant, "Conceptually, an
Endinanness check mu
On 9/6/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
Actually it's not invalid to compile it. That's what a cross-compiler
does. It's invalid to run it. CMake already has this distinction
between TRY_COMPILE and TRY_RUN, so if TRY_RUN is used inappropriately,
that's user error. If CMak
17 matches
Mail list logo