Yep, I guess it is not the same doing a check out from windows (whatever the
tool) and from Cygwin.
-Message d'origine-
De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil]
Envoyé : jeudi 26 septembre 2013 19:29
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
Yeah I'm Windows with TortoiseGit, didn't have to change anything out of the
box for that. It's setup to translate into Windows cr/lf and then back again
automatically.
-Original Message-
From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
It depends the OS, on Windows it is recom
origine-
De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Envoyé : jeudi 26 septembre 2013 19:24
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
It depends the OS, on Windows it is recommended to set it to "true",
"input" on others but if you're on win
: jeudi 26 septembre 2013 19:20
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
Just a small note. The git property changes are independent of the sdk
specifically and more geared toward which git client you use on how to
change the properties.
-Original Message-
From
Just a small note. The git property changes are independent of the sdk
specifically and more geared toward which git client you use on how to change
the properties.
-Original Message-
From: Maurice Amsellem [mailto:maurice.amsel...@systar.com]
6) Fred told me I should set " core.auto
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 26 septembre 2013 18:58
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
Hi,
This is my (uncensored :-) feedback following the SDK build.
1) Doc inconsistency:
There
d to the WIKI.
Regards,
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : jeudi 26 septembre 2013 18:32
À : dev@flex.apache.org
Objet : Re: Building the SDK from git
On 9/26/13 9:12 AM, "Maurice Amsellem" wrote:
>BUILD SUCCESSFUL!
>
>YEE
River Song would say: "Spoilers!" The bane of time travellers all over
the universe...
;-)
EdB
On Thu, Sep 26, 2013 at 6:32 PM, Alex Harui wrote:
>
>
> On 9/26/13 9:12 AM, "Maurice Amsellem" wrote:
>
>>BUILD SUCCESSFUL!
>>
>>YEEHAA!
>>
>>Do you me to recap the few issues I have faced as a "n
On 9/26/13 9:12 AM, "Maurice Amsellem" wrote:
>BUILD SUCCESSFUL!
>
>YEEHAA!
>
>Do you me to recap the few issues I have faced as a "newbie"?
Sure. I think you'll be getting write access soon, so then you'll be able
to update the README yourself.
-Alex
BUILD SUCCESSFUL!
YEEHAA!
Do you me to recap the few issues I have faced as a "newbie"?
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 26 septembre 2013 17:42
À : dev@flex.apache.org
Objet : RE: Building the SDK f
ne-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : jeudi 26 septembre 2013 17:04
À : dev@flex.apache.org
Objet : Re: Building the SDK from git
Hi,
> Please can you share how you proceed to compile when you make even small
> changes to the code and would like to test them.
The Mustella test suite is run on the VM against FP 11.1, 11.7, 11.8
and 11.9; each at least once every two days. These versions appear all
equal in the eyes of the SDK.
EdB
On Thu, Sep 26, 2013 at 5:06 PM, Justin Mclean wrote:
> Hi,
>
>> However playerglobal.version is still 11.1. Does this
Hi,
> However playerglobal.version is still 11.1. Does this mean I should compile
> agains FP 11.1?
You can compile against any version of the Flash Player from 10.2 onwards, we
try and keep it backwards compatible. People who use AIR generally want the
latest, people who use Flash Player may
Hi,
> Please can you share how you proceed to compile when you make even small
> changes to the code and would like to test them.
> Are you using an IDE at all ?
I normally use Flash Builder to edit files (but sometimes vi from the command
line) and I normally compile using ant from the command
be using 11.8.
Which one is correct?
Or maybe it does not matter...
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : jeudi 26 septembre 2013 15:12
À : dev@flex.apache.org
Objet : Re: Building the SDK from git
Hi,
With TLF enviro
che.org
Objet : Re: Building the SDK from git
Hi,
> Yes, I think that is the idea... I think "we" somehow all ended up
> with it in our local ignores
It's not in mine and I've not seen any issues, but they probably shouldn't be
in there in the first place, given ant is the preferred build method.
Thanks,
Justin
Hi,
> Yes, I think that is the idea... I think "we" somehow all ended up
> with it in our local ignores
It's not in mine and I've not seen any issues, but they probably shouldn't be
in there in the first place, given ant is the preferred build method.
Thanks,
Justin
Hi,
> So maybe they should be included in the .gitignore (along with .project,
> etc.) ?
-1 to that. Anything that is actually in version control should not be in
.gitignore, this has caused far too many issues in the past, including breaking
a release candidate.
IMO if something in version c
3 15:56
À : dev@flex.apache.org
Objet : Re: Building the SDK from git
Yes, I think that is the idea... I think "we" somehow all ended up with it in
our local ignores, a legacy from the rather messy transition from SVN.
Also, you raise a couple of good issues with the README and ot
; De : Erik de Bruin [mailto:e...@ixsoftware.nl]
> Envoyé : jeudi 26 septembre 2013 15:45
> À : dev@flex.apache.org
> Objet : Re: Building the SDK from git
>
> On purpose, we don't want IDE specific configuration files in git.
>
> EdB
>
>
>
> On Thu, Sep 26, 2013 a
Understood.
So maybe they should be included in the .gitignore (along with .project, etc.) ?
Maurice
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl]
Envoyé : jeudi 26 septembre 2013 15:45
À : dev@flex.apache.org
Objet : Re: Building the SDK from git
On purpos
is it on purpose ?
>
> Maurice
>
>
> -Message d'origine-
> De : Justin Mclean [mailto:jus...@classsoftware.com]
> Envoyé : jeudi 26 septembre 2013 15:12
> À : dev@flex.apache.org
> Objet : Re: Building the SDK from git
>
> Hi,
>
> With TLF environment var
: dev@flex.apache.org
Objet : Re: Building the SDK from git
Hi,
With TLF environment variables work fine.
On OSX I have the following:
TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/
AIR_HOME=/Users/justinmclean/Documents/air/mac/3.1/
PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/p
Hi,
> Which source is the most up-to-date ?
You want the develop branches of both the SDK and TLF.
Thanks,
Justin
Hi,
With TLF environment variables work fine.
On OSX I have the following:
TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/
AIR_HOME=/Users/justinmclean/Documents/air/mac/3.1/
PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/
FLASHPLAYER_DEBUGGER=/Users/justinmclean/Documents/Adobe
com]
Sent: Thursday, September 26, 2013 8:37 AM
To: dev@flex.apache.org
Subject: RE: Building the SDK from git
I have started reading the wiki on "Setting up Manually", and it says :
TLF: git clone [https://git-wip-us.apache.org/repos/asf/flex-tlf.git] flex-tlf
SDK: git clone [https://g
: dev@flex.apache.org
Objet : RE: Building the SDK from git
Both are good, the build script is able to take either flex-sdk or sdk,
flex-tlf or tlf but you can have troubles run the script if at your first
checkout the "autocrlf" in your /.gitconfig was not set to "input"
-Message d&
lem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 26 septembre 2013 14:37
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
I have started reading the wiki on "Setting up Manually", and it says :
TLF: git clone [https://git-wip-us.apache.org/repos/asf/flex-tlf.git]
flex-
https://git-wip-us.apache.org/#contents
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 26 septembre 2013 14:31
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
Yes, I am on the develop branch.
I have also read the basic
s the same.
-
Which source is the most up-to-date ?
Maurice
-Message d'origine-
De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil]
Envoyé : jeudi 26 septembre 2013 14:11
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
I use...
[anypath]/flex-sdk
[anypath]/fle
urice
-Message d'origine-
De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Envoyé : jeudi 26 septembre 2013 14:27
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
Also, be sure to be on the develop branch "git checkout develop" and the wiki
will tel
.org
Objet : RE: Building the SDK from git
Actually, the README says that TLF_HOME is optional if the tlf directory is a
sibling of sdk.
This is my directory configuration:
ApacheFlex/git_source/
sdk/
tlf/
And I still get an error when running the build "TLF_HOME is not defined".
Mauri
3 14:04
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
Actually, the README says that TLF_HOME is optional if the tlf directory is
a sibling of sdk.
This is my directory configuration:
ApacheFlex/git_source/
sdk/
tlf/
And I still get an error when running the build "TLF
--
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 26 septembre 2013 14:04
À : dev@flex.apache.org
Objet : RE: Building the SDK from git
Actually, the README says that TLF_HOME is optional if the tlf directory is a
sibling of sdk.
This is my directory configurat
nsion Manager CS5.exe
My mustella/local.properties
sdk.dir=F:/sources/apache/flex/sdk
shell=C:/cygwin64/bin/sh.exe
-Fred
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 26 septembre 2013 14:04
À : dev@flex.apache.org
Objet : RE: Buildi
26, 2013 8:04 AM
To: dev@flex.apache.org
Subject: RE: Building the SDK from git
Actually, the README says that TLF_HOME is optional if the tlf directory is a
sibling of sdk.
This is my directory configuration:
ApacheFlex/git_source/
sdk/
tlf/
And I still get an error when running the build
e Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 26 septembre 2013 13:54
À : dev@flex.apache.org
Objet : Building the SDK from git
Hi,
I am trying to build the develop SDK from git.
So I followed the instructions in the README file, and noticed some things that
seem not to be as expected:
1) R
Hi,
I am trying to build the develop SDK from git.
So I followed the instructions in the README file, and noticed some things that
seem not to be as expected:
1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in
env.properties.
All vars are referenced and explained in env-templ
On 9/2/13 12:45 PM, "Harbs" wrote:
>If I'm not mistaken, building the sdk works, but building tlf directly
>does not work if the sdk is not named flex-sdk.
>
>This is a line from build.xml in TLF:
>
>
>Of course this could be overridden, but keeping the
03
À : Dev@Flex
Objet : Re: Building the SDK
Am I the only person who just dumps all my GIT repo sources into a simple
root folder GIT\Flex-SDK and GIT\Flex-TLF ?
-Mark
On Mon, Sep 2, 2013 at 3:56 PM, Frédéric THOMAS
wrote:
> Ok, so, it is easy to make it accept other names, actually, we hav
Am I the only person who just dumps all my GIT repo sources into a simple
root folder GIT\Flex-SDK and GIT\Flex-TLF ?
-Mark
On Mon, Sep 2, 2013 at 3:56 PM, Frédéric THOMAS wrote:
> Ok, so, it is easy to make it accept other names, actually, we have
> flex-sdk
> and sdk, doing so is more flexi
e that tomorrow if nobody disagree.
-Fred
-Message d'origine-
De : Harbs [mailto:harbs.li...@gmail.com]
Envoyé : lundi 2 septembre 2013 21:46
À : dev@flex.apache.org
Objet : Re: Building the SDK
If I'm not mistaken, building the sdk works, but building tlf directly does
not wor
If I'm not mistaken, building the sdk works, but building tlf directly does not
work if the sdk is not named flex-sdk.
This is a line from build.xml in TLF:
Of course this could be overridden, but keeping the same directory names can't
be a bad idea… ;-)
On Sep 2, 2013, at 10:17 PM
js/jx yet
If nobody has problems with that, I'll commit it tomorrow.
-Fred
-Message d'origine-
De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Envoyé : lundi 2 septembre 2013 17:12
À : dev@flex.apache.org
Objet : RE: Building the SDK
Harbs,
I'm in the process to i
ssage d'origine-
De : Harbs [mailto:harbs.li...@gmail.com]
Envoyé : lundi 2 septembre 2013 17:07
À : dev@flex.apache.org
Objet : Re: Building the SDK
> First question: Are you using the develop branch in TLF? And building by
> just running "ant" from the sdk's te
> First question: Are you using the develop branch in TLF? And building by
> just running "ant" from the sdk's textLayout folder? I'm not having
> these issues. I don't know what will happen if you run the build.xml in
> the TLF repo. I've never done it.
Yes. That's right.
The missing type d
On 9/2/13 6:05 AM, "Harbs" wrote:
>BTW, I get a number of build warnings when building tlf:
>1) ParagraphElement has two places where currentAtomIndex has no type
>declaration.
>2) A bunch of calls to TextLine.flushAtomData() does nothing.
>3) A couple of these warnings: ApplyElementStyleNameOp
On 9/2/13 5:26 AM, "Harbs" wrote:
>
>You should now be able to edit and debug the TLF source. When you rebuild
>the swc after editing the source, the correct swc should be linked.
>
>You will need to repeat steps 8-11 for every project you want to debug
>tlf code with.
>
>HTH,
>Harbs
>
>P.S. Shoul
BTW, I get a number of build warnings when building tlf:
1) ParagraphElement has two places where currentAtomIndex has no type
declaration.
2) A bunch of calls to TextLine.flushAtomData() does nothing.
3) A couple of these warnings: ApplyElementStyleNameOperation' has been
deprecated. Please use
Okie Dokie!
I'm finally up and running. Here's what I did in case it's useful to someone
else having trouble with this:
1) Make sure your local repro names match the origin repro names exactly. (i.e.
they should be called "flex-sdk" and "flex-tlf").
2) Makes sure the repros are both in the same
Okay. Thanks.
I'll give it another go later today…
On Sep 2, 2013, at 9:22 AM, Alex Harui wrote:
>
>
> On 9/1/13 10:57 PM, "Harbs" wrote:
>
>> I'm going around in circles hereŠ
>>
>> I have two problems. One with playerglobal.swc and another with
>> textLayout.swc
>>
>> 1) When I link the
Hi,
> I guess I'd suggest using the Installer to set up a working SDK then copy
> textLayout.swc into the working SDK's frameworks/libs folder. But even
> then, I think you have to worry about FB caching the SWC.
From my experience it doesn't cache the framework swcs that often (generally a
ant
On 9/1/13 10:57 PM, "Harbs" wrote:
>I'm going around in circles hereŠ
>
>I have two problems. One with playerglobal.swc and another with
>textLayout.swc
>
>1) When I link the develop SDK to a project, I get two swc links:
>playerglobal.swc and "11.1". It can't find either of those. I can manage
On 9/1/13 10:59 PM, "Harbs" wrote:
>Okay. How do I do that?
>
>You are referring to build.xml in the tlf folder. Right?
No. I've tried to do that and never figured it out. Instead:
1) Go to Project/Properties/Build Paths
2) Open the SDK folder
3) Open the textLayout.swc entry
4) Click on Sourc
Here's what I see in the build.xml:
IMXMLObject
Okay. How do I do that?
You are referring to build.xml in the tlf folder. Right?
On Sep 2, 2013, at 8:50 AM, Alex Harui wrote:
> On second thought, you may need to set up the source attachment in your
> build properties.
I'm going around in circles here…
I have two problems. One with playerglobal.swc and another with textLayout.swc
1) When I link the develop SDK to a project, I get two swc links:
playerglobal.swc and "11.1". It can't find either of those. I can manage to get
the SDK to work by unlinking those a
On 9/1/13 10:30 PM, "Alex Harui" wrote:
>
>
>On 9/1/13 10:21 PM, "Harbs" wrote:
>
>>Okay. Makes sense.
>>
>>And how do you set breakpoints in the code?
>I'm not using FB. FDB allows me to set breakpoints just fine. FB should
>too given that it will use the path in the SWC that you built on y
On 9/1/13 10:21 PM, "Harbs" wrote:
>Okay. Makes sense.
>
>And how do you set breakpoints in the code?
I'm not using FB. FDB allows me to set breakpoints just fine. FB should
too given that it will use the path in the SWC that you built on your
machine so it should be an exact match.
>
>Does i
hich might cache the SWC and require restarts
> after each ant run.
>
>>
>> On Sep 2, 2013, at 12:58 AM, Justin Mclean wrote:
>>
>>> Hi,
>>>
>>>> Is the TLF source files supposed to be copied to the flex sdk folder
>>>> when building the sdk?
>>> No, it's left where it is.
>>>
>>> Justin
>>>
>>
>
which might cache the SWC and require restarts
after each ant run.
>
>On Sep 2, 2013, at 12:58 AM, Justin Mclean wrote:
>
>> Hi,
>>
>>> Is the TLF source files supposed to be copied to the flex sdk folder
>>>when building the sdk?
>> No, it's left where it is.
>>
>> Justin
>>
>
So how does Flash Builder know where the source is?
On Sep 2, 2013, at 12:58 AM, Justin Mclean wrote:
> Hi,
>
>> Is the TLF source files supposed to be copied to the flex sdk folder when
>> building the sdk?
> No, it's left where it is.
>
> Justin
>
Hi,
> Is the TLF source files supposed to be copied to the flex sdk folder when
> building the sdk?
No, it's left where it is.
Justin
older when
building the sdk?
On Sep 2, 2013, at 12:47 AM, Justin Mclean wrote:
> HI,
>
>> I redid everything from scratch. Everything went smoother this time, but I
>> still can not connect to the TLF source.
>
> Probably a silly question but is TLF_HOME correctly set?
>
> Justin
HI,
> I redid everything from scratch. Everything went smoother this time, but I
> still can not connect to the TLF source.
Probably a silly question but is TLF_HOME correctly set?
Justin
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)
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 version
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 gettin
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
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/De
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 hid
Use set command to dump environment. Maybe a hidden char in there?
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Harbs wrote:
Still no go:
Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERG
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
v
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
Never mind. I was missing Documents from the path. Removing the space helps,
but it is still not working:
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.
Bah. Removing the space did not help:
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a
Nope. Escaping the paths does not help. (The variable cannot be set at all.)
I guess I'll remove the space in the paths…
On Sep 1, 2013, at 4:00 PM, Harbs wrote:
> Okay. Getting somewhere…
>
> It looks like it's splitting the space into two separate paths:
> ls: /Users/harbs/Apache: No such fil
Okay. Getting somewhere…
It looks like it's splitting the space into two separate paths:
ls: /Users/harbs/Apache: No such file or directory
ls: Flex/Dependencies/player/: No such file or directory
Does the build script not support vars with spaces? Do I need to double escape
the variable?
I'm s
Hi,
Your structure looks fine, double check the env variable are full paths not
relative, otherwise it may be that there's still an issue with spaces in paths
in the build files.
Justin
Hi,
> The variable is set:
> echo $PLAYERGLOBAL_HOME
> /Users/harbs/Apache Flex/Dependencies/player/
>
> And the file structure looks like this:
> /Users/harbs/Apache Flex/Dependencies/player/11.1/playerglobal.swc
> (I only added 11.1)
Looks OK to me but try this:
ls $PLAYERGLOBAL_HOME
I get:
1
I'm really not having a lot of luck today…
I tried building TLF separately just to see what happens and it seems to be
looking for "flex-sdk" one level up from TLF:
Buildfile: /Users/harbs/Documents/Apache Flex/git/TLF/build.xml
[echo] FLEX_HOME is /Users/harbs/Documents/Apache Flex/git/TLF
tin Mclean wrote:
> Hi,
>
> BTW building the SDK and even making it a usable SDK leaves git reasonably
> clean. That way you don't always need to do a full build but just build the
> project you need (taking under a minute compared to 7-8 minutes for a full
> build).
>
> Thanks,
> Justin
Ah. The readme… :-X
Thanks for the list of envoronment vars. That was helpful.
Thanks!
Harbs
On Sep 1, 2013, at 2:50 PM, Justin Mclean wrote:
> Hi,
>
>> It's been a while since I tried to build the SDK from source and I don't
>> remember the details.
>
> Just follow the README, basically ch
Hi,
BTW building the SDK and even making it a usable SDK leaves git reasonably
clean. That way you don't always need to do a full build but just build the
project you need (taking under a minute compared to 7-8 minutes for a full
build).
Thanks,
Justin
Hi,
> It's been a while since I tried to build the SDK from source and I don't
> remember the details.
Just follow the README, basically check out the sdk and tlf repos and then set
up the required environment vars and do an "ant main".
Example environment vars on OSX
ANT_HOME=/usr/share/ant
A
e recommended
> process for building the SDK while retaining the ability to debug the
> source? (without messing up the git directories…)
>
> I tried looking around the wiki, but did not see instructions (sorry if I
> missed it). Any pointers would be very much appreciated!
>
> Harbs
It's been a while since I tried to build the SDK from source and I don't
remember the details.
Assuming I have the git repository on my machine, what's the recommended
process for building the SDK while retaining the ability to debug the source?
(without messing up the git d
87 matches
Mail list logo
