Re: [cc65] library path

On Mon, Sep 28, 2009 at 08:56:43PM +0200, Thomas Giesel wrote:
> > These are not inconsistencies but completely different things,
> > because the first one is a make variable used as a path within the
> > makefile, while the second is used as a #define for the C compiler,
> > so it has to follow the rules set within the C program.
>
> Basically both are paths. Both *could* be used to give them to
> -DVAR=\"$(VAR)\" *and* to make functions like $dir if they would be
> assigned w/o quotes.

*That* would definitely be very bad style. Just because it is syntactically
possible doesn't mean that it should be done!

One of the variables is defined by the needs of the C program that is going to
be translated. It is in no way related to any makefile function. The job of
the makefile is just to pass it to the compiler. The other variables are
internal variables of the makefile and their use is defined by the needs of
the makefile. 

> > There is absolutely no way to make these uses consistent.
>
> Yes, there is one, refer to the patch.

Ok, strictly speaking, you're right.

Anyway, let's stop here. There is too much talk about makefiles lately:-)

I've (hopefully) fixed the vsprintf/vsnprintf functions, so if you want to
given them a try again, go ahead!

In the meantime, I will go and create the SVN branch for 2.13. Expected a
release candidate the next few days.

Thanks, everybody, for all your help! Without the support from all you guys,
the new version would be far away!

Regards


        Uz


-- 
Ullrich von Bassewitz                                  uz@musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.