You can use the -dump-config option in FB to dump the config.xml that FB is using to compile your project, and then use that (using the -load-config option) with your command-line build.
I know in regular Eclipse you can build from an ant file, and I'm pretty sure that you can do the same with FB.
Although the doc kind of stinks for the flex ant tasks, they work ok.
[EDIT]- I replied in the comments, but I wanted to flesh out my reply.
Herms is having a problem using -dump-config and -load-config and it kind of points out why the flex ant tasks are better. (I didn't want to be the guy who says "why do you want to do X?", so I just answered the asked question).
Even though their doc is subpar (imo), they're better suited for the task of building
your projects.
There are a couple of gotchas using the flex ant tasks, but for the most part, it's not brain surgery (and really the gotchas are more because the doc sucks).
When I started working on the automated build for our project, I found this site:
http://www.nabble.com/FlexCoders-f16212.html
to be invaluable.
In Eclipse they are called Linked Resources
and can be found in Window (menu) -> Preferences -> General -> Workspace -> Linked Resources
PROJECT_FRAMEWORKS
, however, is "special" in that it is provided by the FlexBuilder plugin on a per-project basis. (FB-16815)
Best Answer
I use solely use ant to build all my Flex applications. I wrote a tutorial on how to set up Flex / Ant in a Linux environment, but much can be translated to windows:
http://blog.apterainc.com/software/setting-up-a-flex-development-enviroment-in-gnulinux/
This link is the Adobe's instructions on how to use ant tasks with Flex (everything from installing to compiling your first Flex application):
http://livedocs.adobe.com/flex/3/html/help.html?content=anttasks_1.html
If you run into any problems, post them here and I will help resolve them.