I've started to compile my projects with ant. The nice thing about
this is that you can externalize the OS specific info into a
separate. [build.properties] file. This is a plain text file with
name value pairs that you tell ant to import. Everyone on your team
can have their own [build.properties] file and ant will use the
relevant file path info. Ant will even convert linebreaks from UNIX
to DOS...
So in the ant build.xml file, add this to the start of your file:
<property file="build.properties"/>
And then in the ant build.properties file define all platform
dependent properties:
flashplayer=/Applications/Macromedia\ Flash\ MX\ 2004/Players/
Debug/SAFlashPlayer
Now back in your ant build.xml file you can refer to the variables
defined in the external build.properties:
<exec executable="${flashplayer}">
<arg value="/${outFile}"/>
</exec>
There are some good tutorials on ant/flash integration on the osFlash
site and ubergeek.com has a set of useful tutorials.
http://ubergeek.tv/article.php?pid=98
http://osflash.org/doku.php?id=ant&s=ant+build+files
Best,
J-C
http://flashcodersny.org
On Sep 29, 2005, at 1:38 PM, Pedro Valentini wrote:
> Hi,
>
> I'm working with Windows and will work in projects of other developer
> that use Mac OS X, so all paths for config files, images etc. don't
> work
> in windows, someone have an Idea about what can I do to resolve this
> problem in all projects??
>
> Thank you
>
> --
>
> Pedro C. Valentini
> [EMAIL PROTECTED]
> +55 (21) 8708-8035
>
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
