|
#1
|
|||
|
|||
Here are my steps (full build)
1. Read VB6 proj name with its path from a file using loop action ----> 1a. Update reference for the %LOOP_VALUE% using a script ----> 1b. Compile %LOOP_VALUE% using Make VB6 action And this is what I do for compiling projects individually Copy 1a and 1b in the same VBP script. Replace %LOOP_VALUE% by the project name with its path and do the same what I have done above. I'm not doing this in a different VBP script, rather in the same script. DLL is created in both the cases. But in the latter case, the DLL produced has no issue. I did a diff between the two DLLs (of the same VB project) and found there are differences (hexadecimal differences). They got to be same, right. But they are different. |
#2
|
|||
|
|||
It's possible for two sequential (no source code change) compiles of the same project to produce an executable file with differences (timestamps or other build-specific info stored in the executable), but all else being equal, they should have the same behavior. I can't explain how steps in a loop would generate executables with different behavior than identical steps not in a loop -- there must be some other difference coming into play. At any rate, it's the VB6 command-line executable (vb6.exe) that compiles projects into executables, not Visual Build itself.
|
#3
|
|||
|
|||
I agree with both the points you mentioned:
There will be ifferences in the two DLLs, atleast timestamp difference. And Make VB6 does nothing but call VB6.exe in turn. BTW, I have not tried/tested running the step group containing only the compile part (i.e group having step 1, 1a and 1b). I have eaither run full build (start to end) or have run only the extra step included to compile a single project. DLL/OCX produced (from full build) have only run time issues (display not proper). Do you think there could be some underlying issue which I'm not able to imagine. Only if I know the root cause of the problem will I be able to find a solution for that. I'm stuck bdaly!! |
#4
|
|||
|
|||
I haven't heard of anything like that before. Could there maybe be some sort of circular dependency between projects that requires a particular build order for everything to work properly?
You might try putting all the projects in a .VBG file (could generate this using the loop you already have and write the filenames out like Project=filename) and building that from a Make VB6 step instead, letting it update references, and see if that makes any difference. |
Tags |
not compiling from vbp , vb6 compilation issue |
|
|