Ant is resolving the symlink too, it seems, so that's no solution.

-Josh

On Mon, Jul 14, 2008 at 4:42 PM, Josh McDonald <[EMAIL PROTECTED]> wrote:

> No love with the quotes, but in case somebody comes across this thread via
> google, I've added this to our build.xml to let people know exactly the
> problem if it's not going to work:
>
>         <fail message="Flex compiler cannot consistently handle paths
> containing spaces, please move this project to a new directory.">
>             <condition>
>                 <contains string="${basedir}" substring=" "/>
>             </condition>
>         </fail>
>
> Cheers,
>
> -Josh
>
>
> On Mon, Jul 14, 2008 at 4:37 PM, Josh McDonald <[EMAIL PROTECTED]> wrote:
>
>> Well builder's not, and I was having a similar problem defining a constant
>> with a space in it this morning. The documentation shows you two ways to do
>> it that may or may not work on the command line, but they definitely don't
>> work from builder.
>>
>> Thanks for the double quote tip, I'll try that and post back.
>>
>> -Josh
>>
>>
>> On Mon, Jul 14, 2008 at 4:07 PM, andrii_olefirenko <[EMAIL PROTECTED]>
>> wrote:
>>
>>> use double quotes ("") when defining and parameters. At least it works
>>> for Windows
>>> and btw Flex and Flex Ant tools are free :)
>>>
>>> --- In [email protected], "Josh McDonald" <[EMAIL PROTECTED]> 
>>> wrote:
>>> >
>>> > Can't really do either, as it comes from ${basedir}
>>> >
>>> > There are a few areas where Flex is decidedly beta-like for a version 3
>>> > product that costs so damned much.
>>> >
>>> > -Josh
>>> >
>>> > On Mon, Jul 14, 2008 at 2:31 PM, shaun <[EMAIL PROTECTED]> wrote:
>>> >
>>> > > Josh McDonald wrote:
>>> > > > Hey guys.
>>> > > >
>>> > > > There *must* be something I'm doing wrong here.
>>> > > >
>>> > > > In my ant build:
>>> > > >
>>> > > >         <compc output="'${bin.dir}/${targetLibrary}'">
>>> > > >             <source-path path-element="${src.dir}"/>
>>> > > >         </compc>
>>> > > >
>>> > > > Now src.dir is:
>>> > > >
>>> > > > /Users/josh/Desktop/Work/Builder workspace/PathwaysVersions/src
>>> > > >
>>> > > > And I'm getting the following error from Ant:
>>> > > >
>>> > > > command line: Error: unknown configuration variable
>>> 'compiler.source-path
>>> > > > /Users/josh/Desktop/Work/Builder,workspace/PathwaysVersions/src'
>>> > > >
>>> > > > Which is clearly just blowing the space out into two different
>>> instances
>>> > > of
>>> > > > the <sp> param. How do I embed quotes or something so this doesn't
>>> > > happen?
>>> > > > I've tried using ' as well as &quot; but with no luck. Any ideas?
>>> > >
>>> > > Escape the space.
>>> > >
>>> > > /Users/josh/Desktop/Work/Builder\ workspace/PathwaysVersions/src
>>> > >
>>> > > If that doesnt work. Create a symlink. :)
>>> > >
>>> > > cheers,
>>> > >  shaun
>>> > >
>>> > > ------------------------------------
>>> > >
>>> > > --
>>> > > Flexcoders Mailing List
>>> > > FAQ:
>>> http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
>>> > > Search Archives:
>>> > > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo!
>>> Groups
>>> > > Links
>>> > >
>>> > >
>>> > >
>>> > >
>>> >
>>> >
>>> > --
>>> > "Therefore, send not to know For whom the bell tolls. It tolls for
>>> thee."
>>> >
>>> > :: Josh 'G-Funk' McDonald
>>> > :: 0437 221 380 :: [EMAIL PROTECTED]
>>> >
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> --
>>> Flexcoders Mailing List
>>> FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
>>> Search Archives:
>>> http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups
>>> Links
>>>
>>>
>>>
>>>
>>
>>
>> --
>> "Therefore, send not to know For whom the bell tolls. It tolls for thee."
>>
>> :: Josh 'G-Funk' McDonald
>> :: 0437 221 380 :: [EMAIL PROTECTED]
>
>
>
>
> --
> "Therefore, send not to know For whom the bell tolls. It tolls for thee."
>
> :: Josh 'G-Funk' McDonald
> :: 0437 221 380 :: [EMAIL PROTECTED]
>



-- 
"Therefore, send not to know For whom the bell tolls. It tolls for thee."

:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: [EMAIL PROTECTED]

Reply via email to