I'm having a problem with my build machine since I have moved to Delphi 10 Seattle. The build machine is producing different results to the IDE despite using MSBuild on the build machine and setting the correct configuration. It does the same thing on my machine, so it's not related to something on the machine. The differences I can see so far are:
I'm having a problem with my build machine since I have moved to Delphi 10 Seattle. The build machine is producing different results to the IDE despite using MSBuild on the build machine and setting the correct configuration. It does the same thing on my machine, so it's not related to something on the machine. The differences I can see so far are:
1) Executable size is different. 39MB command line MSBuild, 35MB IDE build.
2) I get an integer overflow error in the executable produced from the command line whereas this doesn't happen from the executable in the IDE. They are clearly two different executables.
3) A COM DLL when built in the IDE is 22mb whereas it is around 59mb when built on the command line. A little further investigation shows that it is actually adding debug information into the DLL DESPITE debug information being off in the release configuration. If I set the "put debug info in a separate TDS file, I then get the same 22mb file plus a 36mb TDS file. This proves 2 things. debug information is being added, and I have the correct configuration as this change has an effect.
I'm currently studying the ultimate DCC32 call from both to see if there are any differences. There must be, but the command is very long, so it's taking a while.
Any ideas?
1) Executable size is different. 39MB command line MSBuild, 35MB IDE build.
2) I get an integer overflow error in the executable produced from the command line whereas this doesn't happen from the executable in the IDE. They are clearly two different executables.
3) A COM DLL when built in the IDE is 22mb whereas it is around 59mb when built on the command line. A little further investigation shows that it is actually adding debug information into the DLL DESPITE debug information being off in the release configuration. If I set the "put debug info in a separate TDS file, I then get the same 22mb file plus a 36mb TDS file. This proves 2 things. debug information is being added, and I have the correct configuration as this change has an effect.
I'm currently studying the ultimate DCC32 call from both to see if there are any differences. There must be, but the command is very long, so it's taking a while.
Any ideas?
Comments
Post a Comment