Look good to me, see
https://fisheye6.atlassian.com/browse/flex-sdk/frameworks/projects/textLayou
t/build.xml?r=4f20635628acdc09e8739c5f94ec644d20cbd959

-----Message d'origine-----
De : Harbs [mailto:harbs.li...@gmail.com] 
Envoyé : dimanche 1 septembre 2013 23:35
À : dev@flex.apache.org
Objet : Re: Building the SDK

I redid everything from scratch. Everything went smoother this time, but I
still can not connect to the TLF source.

Here's what I have:
git
  flex-tlf
    --etc...
  flex-sdk
    frameworks
      libs
        textLayout.swc (along with all the other swcs)
        player
          (all the versions)
      locale
        en_US
          textLayout_rb.swc (along with all the other rb swcs)
      projects
        textLayout (with no source -- all other projects have source.)

That seems logical to me since TLF is in another repro, but how is the SDK
supposed to find the TLF source?

Harbs

On Sep 1, 2013, at 11:09 PM, Harbs wrote:

> I have a feeling my problems might stem from the fact that my git repro is
named differently.
> 
> I'm re-downloading the whole repro and starting from scratch with the 
> standard names…
> 
> Tomorrow is another day…
> 
> On Sep 1, 2013, at 10:55 PM, Harbs wrote:
> 
>> Okay. I solved this one, but I'm only getting source for core Flex
components. (i.e. I get source for Spark components, but I don't get source
for TLF stuff:
>> "Source could not be found for flashx.textLayout.edit.EditManager in
\Users\harbs\blabla\textLayout.swc"
>> 
>> How do I properly link TLF to the rest of the SDK?
>> 
>> On Sep 1, 2013, at 9:56 PM, Harbs wrote:
>> 
>>> When specifying the paths in env.protperties, the spaces don't cause any
problems.
>>> 
>>> But it looks like my issues are not finished. I get this error when I
try to actually use the SDK:
>>> unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
SDK/frameworks//Users/harbs/Documents/Apache
Flex/Dependencies/player//11.1/playerglobal.swc'
>>> 
>>> I'm not sure where I'm supposed to fix this (really wonky) path…
>>> 
>>> On Sep 1, 2013, at 8:20 PM, Harbs wrote:
>>> 
>>>> I set all the variables in the env.properties file instead of via 
>>>> the command line and that seems to have resolved the problem. 
>>>> Weird…
>>>> 
>>>> Next time I'll try with the spaces and see what happens.
>>>> 
>>>> Harbs
>>>> 
>>>> On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
>>>> 
>>>>> Use set command to dump environment. Maybe a hidden char in there?
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>>>>> 
>>>>> Harbs <harbs.li...@gmail.com> wrote:
>>>>> 
>>>>> 
>>>>> Still no go:
>>>>> 
>>>>> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>>>>> 
>>>>> check-playerglobal-home:
>>>>> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME} [echo] 
>>>>> playerglobal.version is 11.1
>>>>> 
>>>>> BUILD FAILED
>>>>> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The 
>>>>> environment variable PLAYERGLOBAL_HOME is not set to a directory
>>>>> 
>>>>> Total time: 0 seconds
>>>>> 
>>>>> It's been a while since I felt like such an idiot… ;-)
>>>>> 
>>>>> Maybe I'll try to restart my machine a bit later…
>>>>> 
>>>>> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> There's still a space in the path - try removing that? I know it was
an issue early on but thought it had been fixed - perhaps not.
>>>>>> 
>>>>>>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>>>>>> 
>>>>>> Thanks,
>>>>>> Justin
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 

Reply via email to