adobe-source-devel

[Adobe-source-devel] Jamfile changes

[Mat M. <mm...@ad...>]

I submitted some substantial changes to the Jamfiles. Some work still
needs to be done, but the files seem to triggering the right actions
for visual/test md5/test and all of their dependents. A good test is
to cd to adove/visual and issue a bjam command--this should cause a
build of asl_lib_dev, boost_thread, boost_signal, boost_filesystem,
libvisual and the visual app. 

Some of the changes:

  1) Added new Boost Build feature: <asl> with value none or dev.
Right now <asl>dev simply causes ADOBE_SERIALIZATION to be defined.
But by setting this to a feature libraries get built in separate
directories so the adobe/build/Jamfile has been greatly simplified.

  2) Fixed the Jamfile.v2 for boost threads. I am attaching the
patched file here since it didn't make it into the latest drop.

  3) All targets are built with static linking at the moment. This
can be fixed, but boost_thread has some complicated requirements in
this area.

 4) Added a new Jamfile to adobe directory to hold common settings.

 
Projects build successfully with msvc compiler. Some work is needed
for gcc 3.3 on mac and windows. Other platforms untested.
Suggestions/improvements very welcome.

[Adobe-source-devel] Re: Jamfile changes

[Ralph T. <ra...@gm...>]

Is the adobe/test/visual stuff moving? IMO it would be nice to move
libvisual out of test -- it's working well enough in my own code. I
guess we'd probably have to decide on what is public API and what is
private (and ui_core could be private, only accessible through the
factory functions).

Thanks,
  Ralph

On 5/16/05, Mat Marcus <mm...@ad...> wrote:
> I submitted some substantial changes to the Jamfiles. Some work still
> needs to be done, but the files seem to triggering the right actions
> for visual/test md5/test and all of their dependents. A good test is
> to cd to adove/visual and issue a bjam command--this should cause a
> build of asl_lib_dev, boost_thread, boost_signal, boost_filesystem,
> libvisual and the visual app.=20
>=20
> Some of the changes:
>=20
>   1) Added new Boost Build feature: <asl> with value none or dev.
> Right now <asl>dev simply causes ADOBE_SERIALIZATION to be defined.
> But by setting this to a feature libraries get built in separate
> directories so the adobe/build/Jamfile has been greatly simplified.
>=20
>   2) Fixed the Jamfile.v2 for boost threads. I am attaching the
> patched file here since it didn't make it into the latest drop.
>=20
>   3) All targets are built with static linking at the moment. This
> can be fixed, but boost_thread has some complicated requirements in
> this area.
>=20
>  4) Added a new Jamfile to adobe directory to hold common settings.
>=20
> =20
> Projects build successfully with msvc compiler. Some work is needed
> for gcc 3.3 on mac and windows. Other platforms untested.
> Suggestions/improvements very welcome.
>=20
>

Re: [Adobe-source-devel] Re: Jamfile changes

[Sean P. <sp...@ad...>]

The intension is to move the pieces out to asl as they are ready, 
alternatively we could move pieces to /future a little sooner. I don't 
know of anything in visual where the API is quite clean enough that I 
want it in ASL proper yet (getting there though!).

Sean

On May 16, 2005, at 5:57 PM, Ralph Thomas wrote:

> Is the adobe/test/visual stuff moving? IMO it would be nice to move
> libvisual out of test -- it's working well enough in my own code. I
> guess we'd probably have to decide on what is public API and what is
> private (and ui_core could be private, only accessible through the
> factory functions).
>
> Thanks,
>   Ralph
>
> On 5/16/05, Mat Marcus <mm...@ad...> wrote:
>> I submitted some substantial changes to the Jamfiles. Some work still
>> needs to be done, but the files seem to triggering the right actions
>> for visual/test md5/test and all of their dependents. A good test is
>> to cd to adove/visual and issue a bjam command--this should cause a
>> build of asl_lib_dev, boost_thread, boost_signal, boost_filesystem,
>> libvisual and the visual app.
>>
>> Some of the changes:
>>
>>   1) Added new Boost Build feature: <asl> with value none or dev.
>> Right now <asl>dev simply causes ADOBE_SERIALIZATION to be defined.
>> But by setting this to a feature libraries get built in separate
>> directories so the adobe/build/Jamfile has been greatly simplified.
>>
>>   2) Fixed the Jamfile.v2 for boost threads. I am attaching the
>> patched file here since it didn't make it into the latest drop.
>>
>>   3) All targets are built with static linking at the moment. This
>> can be fixed, but boost_thread has some complicated requirements in
>> this area.
>>
>>  4) Added a new Jamfile to adobe directory to hold common settings.
>>
>>
>> Projects build successfully with msvc compiler. Some work is needed
>> for gcc 3.3 on mac and windows. Other platforms untested.
>> Suggestions/improvements very welcome.
>>
>>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_idt12&alloc_id344&op=click
> _______________________________________________
> Adobe-source-devel mailing list
> Ado...@li...
> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel