On 06/19/2010 09:41 AM, Carlos Lopez Gonzalez wrote:
>
>> On Fri, 18 Jun 2010 10:40:46 +0200 Michael Hertling wrote:
>
>> On 06/17/2010 11:29 AM, Carlos Lopez Gonzalez wrote:
>>> Hi,
>>> I'm new to cmake and want to port a C++ project which is now built using
>>> autotools to cmake build system.
I got the source code via SVN from:
https://playerstage.svn.sourceforge.net/svnroot/playerstage/code/player/trunk
For an 'How-To' check:
http://playerstage.sourceforge.net/wiki/Basic_FAQ#How_do_I_get_the_latest_code.3F
:-) Marcus
2010/6/18 David Cole
> On Fri, Jun 18, 2010 at 3:19 AM, Marcu
Dave,
On 20 June 2010 18:02, Dave Partyka wrote:
> When configuring your build set CMAKE_OSX_ARCHITECTURES to both the
> architectures you wish to build. For example 'i386;ppc'. This will produce
> libraries/executables with both architectures embedded in them. You can
> check this by just runni
On 06/19/2010 12:31 PM, Janosch Peters wrote:
> On 2010-06-18 08:29:25 +0200, Michael Hertling said:
>
>> On 06/17/2010 04:23 PM, Janosch Peters wrote:
>>> I have two python frameworks on my mac: Python2.5 which comes with OS
>>> X, and python2.6 from macports. If I just use
>>> FIND_PACKAGE(Pytho
I'm doing exclusively out-of-source builds, so this is perfect. Thank you!
Regards,
-- Clark
On 06/20/10 16:31, Eric Noulard wrote:
> 2010/6/20 Clark Gaebel :
>
>> How would I go about placing a text file in the same directory as a
>> target's output?
>>
>> For example, let's say I have a ta
2010/6/20 Clark Gaebel :
> How would I go about placing a text file in the same directory as a
> target's output?
>
> For example, let's say I have a target called "foo", which creates an
> executable. "foo" has a config file called "foo.conf" that should always
> go in the same directory. At the m
Am 20.06.2010 19:14, schrieb Clark Gaebel:
How would I go about placing a text file in the same directory as a
target's output?
For example, let's say I have a target called "foo", which creates an
executable. "foo" has a config file called "foo.conf" that should always
go in the same directory.
This is OK for the easy case, where the source code doesn't require special
defines to be set depending on the architecture. Some projects define symbols,
such as FOO_PPC or FOO_X86 on the command line, instead of doing the detection
in-source using e.g. __ppc__ or __x86_64__, respectively. In
How would I go about placing a text file in the same directory as a
target's output?
For example, let's say I have a target called "foo", which creates an
executable. "foo" has a config file called "foo.conf" that should always
go in the same directory. At the moment, it resides in the src/
direct
When configuring your build set *CMAKE_OSX_ARCHITECTURES * to both the
architectures you wish to build. For example 'i386;ppc'. This will produce
libraries/executables with both architectures embedded in them. You can
check this by just running the 'file' command on any of the
libraries/executables
Hello,
I would like to build a Mac OS X Universal dmg using cpack, but
currently we're building an i386 - how might we build universal
instead?
Here's our CPack config:
http://code.google.com/p/synergy-plus/source/browse/trunk/cmake/CMakeLists_cpack.txt
Nick
_
11 matches
Mail list logo