[mtasc] Conditional Compilation

[Robert Edgar]

Thanks Ralf,
It read on osflash like you needed cygwin to run it...
++++++++++++++++
Prerequisites
----------------
Please note that the cygwin version relies on the cygwin install. 
So for this reason if you want to run your mtasc.exe from within ant on a
normal command prompt, or perhaps via eclipse, you will be required to add
cygwin's path to your PATH environment variable. 
For example, you should add C:\cygwin\bin;C:\cygwin\lib in order for
programs outside of cygwin to get access to your compiled binary.
++++++++++++++++ 
Maybe I am misreading this but if I am then its confusing.

But its good to knowit doesn't require cygwin and I can just run it as I do
MTASC

I didn't mean my comments on stability as any reflection personally but as a
more general statement about the label "hacked" version of a software, as in
if I am going to say to CompanyA "the only way you can use my code is if you
use a hacked vesion of MTASC" then some are going to object.


Also can I ask from your experience how much slower does it make compilation
are we talking about 2x slower, or 20x, or 200x etc..


Rob 


-----Original Message-----
From: mtasc-bounces at lists.motion-twin.com
[mailto:mtasc-bounces at lists.motion-twin.com] On Behalf Of Ralf Bokelberg
Sent: Saturday, October 15, 2005 10:07 PM
To: MotionTwin ActionScript2 Compiler List
Subject: Re: [mtasc] Conditional Compilation


Hamtasc only needs cygwin, if you want to compile it.
If you are on windows, you can find the latest build inside the bin 
directory.

In my experience it is as stable as mtasc, which doesn't make me wonder, 
because it is build from the same source. Otherwise it wouldn't make 
sense to me anyway, since i make my living by programming actionscript.

Cheers,
Ralf.



Robert Edgar wrote:

> Have to add after looking at HaMTASC that it requires cygwin and other 
> changes if you are using eclipse so using it is out as far as I am 
> concerned.
> 
> Rob
> 
> -----Original Message-----
> From: mtasc-bounces at lists.motion-twin.com
> [mailto:mtasc-bounces at lists.motion-twin.com] On Behalf Of Robert Edgar
> Sent: Saturday, October 15, 2005 4:55 PM
> To: 'MotionTwin ActionScript2 Compiler List'
> Subject: RE: [mtasc] Conditional Compilation
> 
> 
> Alan,
> Thanks for that it hadn't clicked that the cpp was in the download of 
> the "core" package. I checked all the docs and list of files etc on 
> the MinGW site and couldn't find any reference to cpp, looked in the 
> utils, bin utils and other I didn't see it so sort of gave up.
> 
> That said...
> I don't think that this solves the problem from a practical point of 
> view, though I will admit it is a workable preprpocessor.
> 
> Basically I have 500+ files to compile every time I run MTASC, that 
> usually takes only a couple of seconds. I just edit the source files 
> (most often in the IDE), I have a command prompt open to run a batch 
> file to compile and then run the swf. This happens about a thousand 
> times a day :-) It is so simple, fast and convenient.
> 
> I am sure this is no different from many other people.
> 
> So now if have put preprocessor commands inside 5 source files 
> somewhere amongst my various packages. I bascially want the process 
> the same as before, I hit a batch file, wait a couple of seconds and 
> then run the swf, anything more and this is getting in my way.
> 
> So cpp for a start only runs on one file at a time, and you have to 
> tell it which file. So that means that what I need is to have 
> something that will recurse over all my folders and execute cpp before 
> MTASC runs. How do I do that? I have seen that there is HaMTASC, a 
> hacked version of MTASC that will do that and maybe that is the way to 
> go, But..
> a)it is a hacked version of MTASC which concerns me, 
> b)is it otherwise 100% compatible with MTASC and which version(cvs, latest
> stable etc), 
> c)it warns that running cpp like this will severly slow down compilation
> 
> I don't really want to go back to MMC compile speeds just for the sake 
> of a couple of lines of optional code.
> 
> That where I feel a built in or integrated solution in MTASC would be 
> ideal, MTASC is already reading and parsing the source file, how much 
> impact would it have to optionally turn on recognising an IFDEF tag 
> and handling that on the fly? I have no idea, I am not a 
> compiler/parser expert but it doesn't sound like it would be a killer 
> or a lot of work especially as there are open source preprocessors 
> written in OCAML around so the basic leg work has been done. I 
> personally just don't have an interest in writing this type of utility 
> only an interest in using it ( :-) )
> 
> I also feel that this is all just way too hard for the average guy to 
> use so even if I can get it to work for myself its not something I can 
> force on others as the only way to use my code.
> 
> The HaMTASC way of just making it a flag on the command line is ideal, 
> it would be workable it this was in the the main MTASC and it would 
> become practical if a preprocessor was integrated in MTASC so that we 
> don't lose any compilation speed.
> 
> 
> Rob
> 
> -----Original Message-----
> From: mtasc-bounces at lists.motion-twin.com
> [mailto:mtasc-bounces at lists.motion-twin.com] On Behalf Of Alan
> Sent: Saturday, October 15, 2005 3:44 PM
> To: MotionTwin ActionScript2 Compiler List
> Subject: RE: [mtasc] Conditional Compilation
> 
> 
> 
> 
> --- Robert Edgar <robert.edgar at epresenterplus.com> wrote:
> 
> 
>>David,
>>I am with you about cygwin. Basically if it doesn't have a native 
>>win32 binary I wont use it.. Unless its java..
>>
>>I will take a look at the unixtools.
> 
> 
>>I would love to have a preprocessor and one that integrates with MTASC
>>because I dotn want to go back to having coffe breaks every time I 
>>compile.
>>
> 
> 
> Try cpp from the package I linked to earlier; you don't need to take 
> the rest of the package; cpp itself is an .exe; it integrates just 
> fine with mtasc.  Incorporate it into your build process with make or 
> ant or whatever scripting you use.
> 
> I basically agree with Haas about working in Windows: I do everything 
> from an MSYS shell and depend on the other tools like make, sed, awk, 
> perl -- you name it.  But you don't have to go whole hog if you don't 
> want to...
> 
> -A
> 
> --
> MTASC : no more coffee break while compiling
> 
> 
> 
> 
> --
> MTASC : no more coffee break while compiling
> 
> 
> 
> 
> --
> MTASC : no more coffee break while compiling
--
MTASC : no more coffee break while compiling