Re: [cc65] THE Makefile V1.2 available - was: automatic generation of makefile dependencies

From: "thefox xofeht"; on Mon., May 30, 2011; at 03:04 PM -0400
>
> On Sat, May 28, 2011 at 5:18 PM,  <silverdr@wfmh.org.pl> wrote:
> > Isn't it easier/better just to install the lib?
>
> It's kind of a problem for me since I'm using my own customized
> version of the library; so, there would be conflicts. I guess the
> "proper" solution indeed is to set the target as "none".

You can install an empty "nes.lib".  Create the archive with one module,
delete that module, then put the archive where ld65 looks for libraries.
It won't conflict with your custom lib.; and, ld65 won't complain.

>
> On Sat, May 28, 2011 at 11:46 PM, Oliver Schmidt <ol.sc@web.de> wrote:
> >> (of course
> >> make from MinGW/whatever is required, as well). That would mean
> >> replacing mkdir/rmdir/rm/etc. with Windows equivalents when Windows
> >> is detected. It's up to you if you want to pursue that or not.
> >
> > I personally don't see any point in doing so. Where ever you get
> > your make from should be a great place to get mkdir/rmdir/rm from.
>
> Yeah, I understand you completely. In the case of cmd.exe, the problem
> isn't getting mkdir/rmdir/rm, however; it's that it implements
> built-in versions of mkdir/rmdir that (AFAIK) can't be overridden
> without specifying the full path to the executables -- correct me if
> I'm wrong.
>
> Because of that, if nothing else, it might be good to give the user a
> warning if cmd.exe is used; because, there's just no way "mkdir -p" is
> going to work when run from cmd.exe!

To Oliver:

The "mkdir" and "rmdir" commands should be handled in the same way that
"rm" is handled.  Define and use:

MKDIR ?= mkdir -p
RMDIR ?= rmdir

Then, thefox can redefine MKDIR in his permanent environment.

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