Skip to content

Commit ee342a3

Browse files
committed
update install/build instructions
commit "Stop tracking autoconf-generated files." discontinued distributing configure
1 parent 903fbc1 commit ee342a3

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

readme/read1st.txt

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,13 +29,18 @@ Building Dmake
2929
With autotools
3030
--------------
3131
Building dmake on systems that are supported by the autotools build system
32-
only requires the usual "./configure && make && make install" command.
33-
The configure command will notify you when your platform is not supported.
32+
only requires the usual "./autogen.sh && ./configure && make && make install"
33+
command. The configure command will notify you when your platform is not
34+
supported.
3435

3536
With Microsoft C++ compiler
3637
---------------------------
37-
For MS Visual C++ 6 and up run "make.bat win95-vpp40" in a command shell.
38-
This should create a dmake.exe in the top-level directory.
38+
For MS Visual C++ 4 through 6 run "make.bat win95-vpp40" in a command shell.
39+
For MS Visual C++ 2003 and up run "make.bat win95-vpp70" in a command shell.
40+
Both 32 bit and 64 bit builds are supported. The bitness of the dmake build is
41+
determined by the bitness of cl.exe which was found in PATH. Use "vcvars32" or
42+
"vcvarsall x64" to pick the correct Visual C++ compiler. A dmake.exe will be
43+
created in the top-level directory.
3944

4045
It is possible to rename this to, say, dmake0.exe, delete the objects/
4146
sub-directory and then simply run "dmake0.exe" to build a new dmake.exe.

0 commit comments

Comments
 (0)