On Fri, Mar 14, 2003 at 11:37:03AM +0100, Glen Vermeylen wrote:
> [..]
>
> I already knew what your tutorial said, though its much more
> comprehensive than Bruce Eckels' explanation.
OK, sorry for having you read twice the same stuff, currently I
do not know what is in Bruce Eckels' book (haven't read it yet :-)
Also, I apologize for mailing you private, the message was for the
list ... I must have hit the 'r' key instead of the 'l' one.
> Its just that.. well... I can't get make to work.
> Under linux it's just make install, make this, make that... and it
> always works.
That sounds a good reason to develop your application on a GNU/Linux
platform ;-)
> But under windows I'm a bit lost.
>
> The documentation says to "make gcc" in the main directory.
> After inspecting the makefile I see it goes to every subdirectory:
> "gcc:
> cd C02; make -f gcc.makefile
> cd C03; make -f gcc.makefile
> cd C04; make -f gcc.makefile... and so on"
> The gcc.makefile's are probably 100% correct :) .
It looks like you are trying to build the compiler.
I've never done such a thing myself, so I shall give my advice but
can't be 100% sure of what I say, though I'll try to make it sound.
From the above line, I see that the makefile you are using has
lines like:
"command; command"
The above style is not going to work on Dos (whatever) / Windows (up-to
and including Win98SE). I do not know if the shell which ships with
newer versions allows such a thing, but I do not think so.
Probably have downloaded the source package for *nix, as the above syntax
is quite common on Bash or Sh shells.
So now I have a few questions, I hope you don't mind answering:
- which version of Windows are you running ?
- which shell are you using ?
- which brand of Make are you using ? (Microsoft, Borland, GNU, ...)
- which version of Make is it ?
Anyway, I suggest you get the MinGw Msys tools, they include an Sh shell,
so that some stuff from the *nix world may be used on a Windows machine.
You may also go for Cygwin, which is probably better, but I don't know
how that thing works.
> I tried copying everything from dev-cpp\bin to command
Can you elaborate on this? What is "command"?
> source-dir just calling "make gcc".
> Also I tried calling "make
> D:\BACKUP\e-books\BruceEckel\TICPP-2nd-ed-Vol-one-code\C02 gcc" (also
> with backslashes converted to forward slashes).
> I also tried every combination I could think of using c:\dev-cpp\bin\make
> But always I get something like "nothing to be done for target...." or
> "no rule to make target" or something like that.
>
> I guess it would be enough for someone who got it to work under windows
> to say how he calls make (or how he sets it up). I'm not stupid, just
> not used to dos :) .
I never meant such a thing, if my previous mail, where I address you to
my simple (very very elementary) tutorial gave you such an impression,
I shall apologize, I though it was a suitable answer to you question
as you asked a "step-to-step" procedure.
As for setting up Make under Dos/Windows, I think you have it set correctly,
in fact when you type
"make"
It seems that the program shows up, so it exists and its location is
in the path. This brings me to the idea that the problem is not Make but
the fact that you are using the wrong shell.
Have you tried with simple makefiles? A rule I always try to
follow is: put together a simple example, test it, if it does
not work, you may post it and we can see what is wrong.
Remember, if you are attempting to compile some source code
originally designed with *nix in mind, on a Windows machine, do
not expect things to work out of the box.
--
>> gisan >>
|
