CODEWITHSUNDEEP
compilationlinkervb6windows-10
Arvo Bowen
Arvo Bowen

Reputation: 4929

Manually compile VB6 project using LINK.EXE and C2.EXE

I would like to try and avoid the VB6.exe application when trying to compile my project. It tends to create the *.obj files and then crashes leaving me with no idea what went wrong.

"c:\Program Files (x86)\Microsoft Visual Studio\VB98\VB6.EXE" /m MyProject.vbp

I would like to try and use LINK.exe and C2.exe to compile my application instead. I found a really great article located here on the process with all the switches etc. I was hoping someone has tried something link this and been successful so they can tell me exactly what switches I need to use and a step by step process of how to create the object files and then link them all to the EXE.

Upvotes: 3

Views: 4141

Answers (1)

Arvo Bowen
Arvo Bowen

Reputation: 4929

I ended up getting this old source to compile. I'm sure my situation was unique but I thought I would share in hopes of helping someone else find their way if this happens to them.

First, I could NOT get this one project to compile to save my life in the end. At first it would compile in the IDE, then only by running the following in a command line...

"c:\Program Files (x86)\Microsoft Visual Studio\VB98\VB6.EXE" /m MyProject.vbp

Then that would not even work and I had to use the package and deployment wizard to compile it which worked some of the time.

I think it was really just hit or miss in the end. But at some point something pointed to a specific module file I had that was used to access (read/write) the registry. I think it was between looking at logs and maybe even the windows event viewer etc. So I started thinking... Maybe it will compile if that was not used. So I removed the module from the project, tried to compile, then VB was nice enough to show me every call that would not work because the referenced function did not exist. I commented out all of those as well then I was able to compile with very little effort and it went smooth again!

So that helped me identify what VB was flipping out about but it did not solve the underlining issue (that I could not compile ALL of my source). So I started trying to work all the source back into the application one by one to see where it would break at.

  1. I first added the module file to the project and just compiled.

    Success!

  2. I then tried to uncomment the first thing I commented out (reference to the function in that module) and then recompiled.

    Success!

  3. I managed to get all the way back through all my commented out lines of code and put them back the way they were originally. I then recompiled for the final time.

    Success!

So at this point I had EVERYTHING back to the exact way I had it before I started trying to compile. Now it works with no issues at all!

Upvotes: 2

Related Questions