Re: [cc65] building under cygwin

From: MagerValp; on Friday, June 15, 2007; at 08:49 AM -0400
>
> True, but I'm not aware of any current Unix variants that don't support
> it.  I even checked a few flavours that traditionally are late adopters
> (IRIX, HP-UX, etc.), and they all support "-p".  I think it's safe to
> default to "-p".

Some of us happen to use old versions of OSes on old computers.  :-)
So, I made a safe choice:  each path is tested and created separately by
shell expressions.

>
> Again, I think it's safe to default to using install, with install-sh
> as a commented-out fallback for users stuck on systems without it (and,
> out of curiosity, are there any?).

Yes, I'm install-less on an old QNX box (it's the reason why I built that
script).

It's rather difficult for "make" to learn (while decoding the makefile) if
a program is available, but it's easy for the shell to do it.  So now, the
makefile always starts the script; install-sh will switch to install if
that program exists.  Direct, simple, obvious -- so, naturally, it took me
a long, long time to think of it! ;-D

From: silverdr; on Saturday, June 16, 2007; at 04:23 PM -0400
>
> Manual cleaning (and, being sure that nothing gets
omitted/overwritten/deleted)
> is an additional, unnecessary, and error-prone work.

_Manual_ cleaning?!  MagerValp said the same thing.  Is there something
that I forgot to put into the uninstall rule?  Why would you need to clean
out a wrong installation _manually_?

>
> 1. default "prefix" to be /usr/local
> 2. taking care of the LIB and INC paths at the Makefile/build level

1. I like your argument, so I changed it to "/usr/local".
2. That is another one of those things that I did back in February, but
forgot to send to Uz. :-)  (It works in GNU's brand of make -- probably not
in other brands.)
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.