Note that you can also cause an entire directory tree to be compiled in.
This should be used with caution, since it will also try to compile any
"included" helper code as if they were classes, which might not be what
you want.
-rg
________________________________
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Gordon Smith
Sent: Wednesday, February 21, 2007 3:44 PM
To: [email protected]
Subject: RE: [flexcoders] compc - degrees of specification
Resending because this didn't seem to make it through to the
list.
- Gordon
________________________________
From: Gordon Smith
Sent: Wednesday, February 21, 2007 9:15 AM
To: '[email protected]'
Subject: RE: [flexcoders] compc - degrees of specification
A typical way to do this is to first create a "manifest" file
for the components in the library, so that they can be associated with a
namespace of your choosing that is unrelated to your package hierarchy.
(Take a look at the file mxml-manifest.xml in the frameworks directory.
The flex-config.xml file associates this manifest file with the single
namespace http://www.adobe.com/2006/mxml
<http://www.adobe.com/2006/mxml> despite the fact that its classes are
in various packages like mx.controls, mx.containers, etc.)
After you have set up a manifest file, you can use compc's
-namespace and -include-namespaces options to include all the components
in that namespace's manifest (and all the classes that they depend on)
without naming each one:
compc -namespace
http://www.yourcompany.com/flex/coolcomponents
<http://www.yourcompany.com/flex/coolcomponents>
mycoolcomponents-manifest.xml
-include-namespaces
http://www.yourcompany.com/flex/coolcomponents
<http://www.yourcompany.com/flex/coolcomponents>
If there are other classes that should go into your SWC which
aren't listed in your manifest or which the compiler can't discover by
doing a dependency analysis starting from the classes in your manifest,
then you can use the -include-classes option to list them one-by-one.
- Gordon
________________________________
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of alehrens
Sent: Wednesday, February 21, 2007 8:44 AM
To: [email protected]
Subject: [flexcoders] compc - degrees of specification
Hi,
I'm tinkering with using Ant for our flex build... We have two
libraries that contain a good amount of files (say, 25 .as file
and 20
.mxml files for this example).
My questions are:
1. Do I include both types of files in the compc task - to build
everything in our library into one .swc?
2. Is there any way to wildcard it or do I have to specify every
file
out explicitly?
aaron
