Re: [AD] makefile.vc prob

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


hmmm.. in this respect, it would be a very awkward way to define what
sort of variables you exactly want ..


should we decompose n clean up the flags like: ARCH_FLAGS, PROC_FLAGS,
OPT_FLAGS, DEBUG_FLAGS n PROFILE_FLAGS? It would ideally make lot more
sense... and, this is has to be applied across _all_ compilers and
platforms ...

Besides, I was also thinking of writing the compilations in a format like:

$(RUNNER) $(COMP) $(RUNNERSEP) $(OUT)obj-name $(COMPONLY) $(CFLAGS)
$(INCLUDE) $(LIB) ??

(so we can clean up the MinGW/VC files a bit as well..)

On Apr 1, 2005 7:08 AM, Chris <chris.kcat@xxxxxxxxxx> wrote:
> AJ wrote:
> > with the current 4.2.0.RC
> > can you make one little adjustment..
> 
> That doesn't look like a good thing to do. TARGET_ARCH_EXCL is supposed
> to be defined to the target architecture option (ie "pentium",
> "athlon-xp", etc), without the option itself. With that, it basically
> turns it into an option to add CFLAGS, which, if it's going to be done,
> should be handled a cleaner way. IMO, it's fine how it is.
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by Demarc:
> A global provider of Threat Management Solutions.
> Download our HomeAdmin security software for free today!
> http://www.demarc.com/Info/Sentarus/hamr30
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
> 


-- 
Karthik
http://guilt.bafsoft.net




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/