Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of pent@adobe.com designates
 64.18.1.187 as permitted sender)
From: Peter Ent <pent@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Thu, 23 Aug 2012 06:32:54 -0700
Subject: Re: Getting Mustella to work.
Thread-Topic: Getting Mustella to work.
Thread-Index: Ac2BM81oyxujA2P+Q1aFinYLQzO/dA==
Message-ID: <CC5BA7E8.1F7E%pent@adobe.com>
In-Reply-To: 
 <0E7CF6486AC44249B0B674C6760449B402FDE650@mcusquanez26v.mcdsus.mcds.usmc.mil>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

That ought to work, but does not. The Mustella code pieces together a
large string with all of the options on it, then turns the string into a
String[] by using space as the delimiter. Thus

-source-path=3D"C:\Program Files\Common Files\Microsoft
Shared\MSInfo\MSInfo32.exe"

turns into
[] =3D -source-path=3D"C:\Program Files\Common
[] =3D Files\Microsoft
[] =3D Shared\MSInfo\MSInfo32.exe"

And it does this several times (turning the array into a string, inserting
other args, back to an array) to build up the argument list. Ultimately,
the array of options is passed over to mxmlc to execute, so it does need
to turn into an array of options. I was working on putting everything into
an ArrayList but more and more code needed to change and then I was
getting errors from mxmlc saying parameters were being mixed which I
didn't understand since it was getting the same parameters in the same
order.

So I have to re-think the approach.

--peter

On 8/23/12 6:59 AM, "Kessler CTR Mark J" <mark.kessler.ctr@usmc.mil> wrote:

>I know this may sound silly, but windows deals with the spaces in path
>using quotes around the whole path.  Is there something similar with
>Mustella?
>
>So a windows command prompt example, I could do something like the
>following...
>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>
>
>Whereas the old non spaced dos style naming convention would do this
>without quotes..
>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>
>
>r/s
>-Mark
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Wednesday, August 22, 2012 9:20
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>I have not have luck solving the problem. It is much trickier than I
>anticipated. I am going to jump back into getting more tests to run and
>think more about the problem. Operating systems have allowed spaces in
>file names for many, many years and you'd think would be an easily
>solvable problem (or not even a problem at all).
>
>--peter
>
>On 8/21/12 11:12 PM, "Justin Mclean" <justin@classsoftware.com> wrote:
>
>>Hi,
>>
>>If the space path issue was fixed you have more to add. Any luck with
>>that yet?
>>
>>Justin
>