OBJ, LIB and Resource files, Oh my

[The Storm]

Ok, I've been trying to get a couple of things compiled but it seems when I run the mknt.bat file, everything goes well but it doesn't make any type of DLL file. It will, however, give me the LIBs, OBJs, BLDs, Header Files, and Object File Librarys.

Still, no DLL's. Any idea what I might be doing wrong?

Here's my dev environment:

SET CONFIG=WG3DEV
SET WGDEV=D:\WGDEV
SET BC50=D:\BC5
SET COMPILER=D:\BC5
SET WGNT=C:\WGSERV
SET LIB=D:\WGDEV\INC;D:\WGDEV\ENTSRC;D:\BC5\LIB
SET CMP=BC50-32
SET OS=WNT
SET WGPATH=C:\WINDOWS;D:\BC5\BIN;D:\;D:\WGDEV\BIN;C:\WINDOWNS\SYSTEM;c:\WINDOWS\SYSTEM32
SET PATH=C:\WINDOWS;D:\BC5\BIN;D:\;D:\WGDEV\BIN;C:\WINDOWS\SYSTEM;c:\WINDOWS\SYSTEM32;d:\WGDEV\WGTOOLS\BTRIEVE;

[dspain]

Ok, I've been trying to get a couple of things compiled but it seems when I run the mknt.bat file, everything goes well but it doesn't make any type of DLL file. It will, however, give me the LIBs, OBJs, BLDs, Header Files, and Object File Librarys.

Still, no DLL's. Any idea what I might be doing wrong?

Here's my dev environment:

SET CONFIG=WG3DEV
SET WGDEV=D:\WGDEV
SET BC50=D:\BC5
SET COMPILER=D:\BC5
SET WGNT=C:\WGSERV
SET LIB=D:\WGDEV\INC;D:\WGDEV\ENTSRC;D:\BC5\LIB
SET CMP=BC50-32
SET OS=WNT
SET WGPATH=C:\WINDOWS;D:\BC5\BIN;D:\;D:\WGDEV\BIN;C:\WINDOWNS\SYSTEM;c:\WINDOWS\SYSTEM32
SET PATH=C:\WINDOWS;D:\BC5\BIN;D:\;D:\WGDEV\BIN;C:\WINDOWS\SYSTEM;c:\WINDOWS\SYSTEM32;d:\WGDEV\WGTOOLS\BTRIEVE;

compiled DLL's goto $(RUNDIR) which is a shadow of $(WGNT) usually C:\WGSERV

[The Storm]

compiled DLL's goto $(RUNDIR) which is a shadow of $(WGNT) usually C:\WGSERV

Yea, thanks for the heads up. I did find the DLLs there after some searching. Hopefully, this puts me back on the path of getting things done.

[dspain]

compiled DLL's goto $(RUNDIR) which is a shadow of $(WGNT) usually C:\WGSERV

Yea, thanks for the heads up. I did find the DLLs there after some searching. Hopefully, this puts me back on the path of getting things done.

yeah you can also set a batch file to build and set a path called $(PROJDIR) and replace $(RUNDIR) in the mak file with $(PROJDIR) and output all binaries there.

[The Storm]

yeah you can also set a batch file to build and set a path called $(PROJDIR) and replace $(RUNDIR) in the mak file with $(PROJDIR) and output all binaries there.

Might be a better idea since I don't want to hose my dev environment so early into development.

[dspain]

yeah you can also set a batch file to build and set a path called $(PROJDIR) and replace $(RUNDIR) in the mak file with $(PROJDIR) and output all binaries there.

Might be a better idea since I don't want to hose my dev environment so early into development.

no reason to hose. another thing you can do is have $(WGNT) point to a dir other than your actual server that way DLL's wont be placed in the main dev server directory.
i output all my compiled binaries in a BIN folder off of $(GCBUILD)
keeps em all there and i have my installshield compiler point to the project's GCBUILD\BIN dir.

@echo off
SET PROJDIR=C:\WGDEV\ISV\PROJECT
mknt PROJECT.MAK
set PROJDIR=

within your projects.mak file point the 2 $(RUNDIR) vars to $(PROJDIR)