On Mon, 2014-01-20 at 07:06 -0800, Uwe wrote:
> I found a quite simple solution:
>
> call make with the -R Option which suppresses all built-in stuff ...
That can't be a valid solution, given the makefile you provided before.
If you suppress the built-in rules then there will be no rules that k
I found a quite simple solution:
call make with the -R Option which suppresses all built-in stuff ...
--
View this message in context:
http://gnu-make.2324884.n4.nabble.com/strange-behavior-with-makefile-tp15127p15131.html
Sent from the Gnu - Make - W32 mailing list archive at Nabble.com.
_
> From: Paul Smith
> Date: Mon, 20 Jan 2014 08:17:43 -0500
> Cc: Make-w32@gnu.org
>
> As for why the "/" instead of "\", make is a POSIX tool and it deals
> with "/" as a directory separator. The Windows port of make has some
> facilities to read Windows paths instead, but when make constructs a
On Mon, 2014-01-20 at 00:45 -0800, Uwe wrote:
> I am just before getting mad with that makefile. I already shortened my
> large makefile to just a few lines:
> SRC_DIR = ..\src
> OUT_DIR = ..\out
> TMP_DIR = ..\tmp
> # Compiler
> CC = ..\..\tools\compiler\cx6808
> CFLAGS = -pp -vl +nowiden
Hi,
I am just before getting mad with that makefile. I already shortened my
large makefile to just a few lines:
*makefile:*
TARGET = TEST
SRC_DIR = ..\src
OUT_DIR = ..\out
TMP_DIR = ..\tmp
vpath %.c $(SRC_DIR)
# Compiler
CC = ..\..\tools\compiler\cx6808
CFLAGS = -
