Thanks.
But the problem's solved - at least for the moment. I edited PREFIX in
makefile.auto, ignoring the warning about it being an automatically-generated
file, and typed 'make' and it decided to do its thing.
Still, your idea sounds good. I'll keep it in mind.
Wesley Parish
On Sat, 15 Oct 2005 23:21, Horváth Róbert wrote:
on gentoo I used to create the install cd with these
commands:
export ROS_PREFIX=i386-mingw32msvc
export PATH=$PATH:/opt/xmingw/bin
make bootcd
you should:
export ROS_PREFIX=i586-mingw32msvc and export PATH=$PATH:<folder of your
mingw installation>
talley
ps: you should read the beginning of the trunk/reactos/Makefile. it
contains a lot of inromation.. like:
# Accepted environment variables:
#
# ROS_PREFIX
# This variable specifies the prefix of the MinGW installation.
On Windows
# a prefix is usually not needed, but on linux it is usually
"mingw32". If
# not present and no executable named "gcc" can be found, then
the prefix is
# assumed to be "mingw32". If your gcc is named i386-mingw32-gcc
then set
# ROS_PREFIX to i386-mingw32. Don't include the dash (-) before gcc.
Wesley Parish wrote:
I started compiling ReactOS 0.2.7 on my Linux
box
uname -a
Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 Celeron
(Coppermine) unknown GNU/Linux
This was the result.
I'm using i586-mingw32mscv-*. Now my question is, in which file do I
find the elusive (PREFIX)? Because I can't find it in Makefile.
...
make: mingw32-dlltool: Command not found
make: *** [obj-i386/lib/kernel32/libkernel32.a] Error 127
[wparish@localhost reactos027]$
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
--
Clinersterton beademung, with all of love - RIP James Blish
-----
Mau e ki, he aha te mea nui?
You ask, what is the most important thing?
Maku e ki, he tangata, he tangata, he tangata.
I reply, it is people, it is people, it is people.