<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
----- Original Message -----<br>
From: Brandon Van Every<br>
Date: 2/5/2008 7:23 AM
<blockquote
cite="mid:36a55ab0802050623i218664aft4b6d298e84d2027f@mail.gmail.com"
type="cite">
<pre wrap="">On Feb 5, 2008 6:50 AM, John Spray <a class="moz-txt-link-rfc2396E" href="mailto:john.c.spray@googlemail.com"><john.c.spray@googlemail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Is it possible to build certain objects for one architecture and
certain objects for another?
</pre>
</blockquote>
<pre wrap=""><!---->Not in the same build. You'd need 2 different invocations of CMake.
You could have 1 CMake use an execute_process to call the other CMake.
The foreign build would need to output a library that the host build
recognizes as usable. Otherwise you'd have to take over linking
manually with some kind of add_custom_command, however you usually get
it to work. Why do you need the foreign code embedded in the host
library? Wouldn't shipping libraries for multiple platforms be
enough?
</pre>
</blockquote>
I'll give a simple example, if I'm understanding the request. For the
PS3, you link SPU code in the PPU executable. SPU code is just .c/.cpp
files, possibly with libraries linked in. In any case, there are two
separate toolchains needed, one for PPU code and one for SPU code.<br>
<br>
In the build system I use for this, it looks something like this:<br>
<br>
AddExecutable the_ppu_program :<br>
sourcefile1.c<br>
sourcefile2.c<br>
[ AddSPUProgram spu_program_1 : spufile1.c spufile2.c ]<br>
[ AddSPUProgram spu_program_2 : spufile1.c spufile3.c ]<br>
;<br>
<br>
Josh<br>
</body>
</html>