Afforess
The White Wizard
No; Jdog or whomever removed all the CvXImage stuff from RevDCM a while ago.
Improved CvGameCoreDLL Makefile! AND ~71% faster compilation
- Thread starter DannyDaemonic
- Start date
EmperorFool
Deity
CxImage is to allow Map Finder to do screenshots.
I removed the folder and all references to it, and now it works.
Valkrionn
The Hamster King
ripple01
Emperor
Hello,
I'm trying to use this makefile with no success. I'm following the instructions on the Modiki and am running into the following error:
1>------ Build started: Project: CvGameCoreDLL, Configuration: Debug Win32 ------
1>
1> Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
1> Copyright (C) Microsoft Corporation. All rights reserved.
1>
1>NMAKE : fatal error U1073: don't know how to make 'release'
1> Stop.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.MakeFile.Targets(38,5): error MSB3073: The command "nmake release" exited with code 2.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
I'm sure I'm missing something blatantly easy, but I can't come up with it. Any suggestions? I'm using VS2010.
Cheers,
ripple01
I'm trying to use this makefile with no success. I'm following the instructions on the Modiki and am running into the following error:
1>------ Build started: Project: CvGameCoreDLL, Configuration: Debug Win32 ------
1>
1> Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
1> Copyright (C) Microsoft Corporation. All rights reserved.
1>
1>NMAKE : fatal error U1073: don't know how to make 'release'
1> Stop.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.MakeFile.Targets(38,5): error MSB3073: The command "nmake release" exited with code 2.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
I'm sure I'm missing something blatantly easy, but I can't come up with it. Any suggestions? I'm using VS2010.
Cheers,
ripple01
Valkrionn
The Hamster King
You didn't change the make commands.
Essentially, everywhere in that guide where it says "Final_Release", change it to "Release".
Where it says clean_Debug and clean_Final_Release, change it to Debug_clean and Release_clean.
I think that's it.
Essentially, everywhere in that guide where it says "Final_Release", change it to "Release".
Where it says clean_Debug and clean_Final_Release, change it to Debug_clean and Release_clean.
I think that's it.
ripple01
Emperor
Thanks for the quick reply. I did as you said and am still getting an error message:
1>------ Rebuild All started: Project: CvGameCoreDLL, Configuration: Release Win32 ------
1>
1> Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
1> Copyright (C) Microsoft Corporation. All rights reserved.
1>
1>NMAKE : fatal error U1073: don't know how to make 'release_clean'
1> Stop.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.MakeFile.Targets(33,5): error MSB3073: The command "nmake release_clean" exited with code 2.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========
I've attached a screen of my nmake config if it helps at all.
Cheers,
ripple01
Attachments
Valkrionn
The Hamster King
Only difference from mine is that it is Release, not release. Same goes for Debug.
ripple01
Emperor
I tried that, and it didn't seem to make a difference. Thanks for the suggestion, though. Maybe someone else will have another idea I can try.
Cheers,
ripple01
Archid
Warlord
When I tried to create a debug build I got an error around the module size of CyCityInterface1.cpp. I saw that Afforess had the same problem and had moved a chunk of the defines into a second file: CyCityInterface2.cpp.
The compilation went through fine, but I am getting errors where the Python code cannot access the defines that I moved to CyCityInterface2.cpp. Is there anything else that I need to do other than just copy the file, change the class name and split the .def() lines? I have tried a clean and a full build.
I used the CyGlobalContextInterfaceX.cpp files as an example and used the following.
I know that this is a bit off-thread but others may run into the same issue when creating a debug build using this new makefile. If it not related to this makefile then I will move the post over to a new thread.
Cheers,
Jim
The compilation went through fine, but I am getting errors where the Python code cannot access the defines that I moved to CyCityInterface2.cpp. Is there anything else that I need to do other than just copy the file, change the class name and split the .def() lines? I have tried a clean and a full build.
I used the CyGlobalContextInterfaceX.cpp files as an example and used the following.
PHP:
void CyCityPythonInterface1(python::class_<CyCity>& x)
{
OutputDebugString("Python Extension Module - CyCityPythonInterface1\n");
x
.def("isNone", &CyCity::isNone, "void () - is the instance valid?")
// rest of .def() definitions here
.def("getEspionageDefenseModifier", &CyCity::getEspionageDefenseModifier, "int ()")
;
}
void CyCityPythonInterface2(python::class_<CyCity>& x)
{
OutputDebugString("Python Extension Module - CyCityPythonInterface2\n");
x
.def("isWorkingPlotByIndex", &CyCity::isWorkingPlotByIndex, "bool (iIndex) - true if a worker is working this city's plot iIndex")
// rest of .def() definitions here
.def("isHasBuildingClass", &CyCity::isHasBuildingClass, "bool (int /*BuildingClassTypes*/ eBuildingClass)")
;
}I know that this is a bit off-thread but others may run into the same issue when creating a debug build using this new makefile. If it not related to this makefile then I will move the post over to a new thread.
Cheers,
Jim
Archid
Warlord
Did you also add your new CyCityInterface2 to CvDLLPython? Just search for CyCityPythonInterface1 and you should find where you should add them.
PS: I had the same problem.
Thanks...that cured it
Valkrionn
The Hamster King
Actually, I had the exact same problem as well. 
DannyDaemonic
Chieftain
- Joined
- Jun 6, 2010
- Messages
- 25
I have a suggestion, use the VS2010 project files! I've just attached them to the original post. Let me know if they work for you. I am also thinking about building project files for other versions of Visual Studio. I might not get around to it though.
I was also thinking of packaging up the whole project, source and all, just to make it easier. Preferably with the unofficial patch. But, lets just try this to start.
ripple01
Emperor
EmperorFool
Deity
I was way too busy IRL to do more than read this thread, so I apologize for the late entry into the discussion. I'm setting BULL up to use your makefile finally and had some thoughts during the process. Let me say first a big "thank you" for doing this as it was needed. 
Breaking up CyCityInterface.cpp
I got the error about the debugging information overflow with this file, so I checked the compiler settings. Some of the options in your makefile are redundant, and some differ in ways that I'd like to understand further.
You had these extra options:
I could only find "/Gm" which enabled minimal rebuild. I assume it's off by default, but the docs didn't list the - option to this feature.
/Zi seems to be what kills CyCityInterface1.cpp. I'm trying other /Z settings but will probably end up splitting the original file as everyone else has. It might be nice to supply a pre-split file.
The main difference (not listed above) however is that I use /MDd for debug builds and link against MSVCPRTD.lib which is supposed to be for debugging. That requires "/NODEFAULTLIB:msvcprtd.lib" in the debug libs. Do you know if this is necessary? It's been a long time since I put together BULL's makefile using the original from Refar, and I had a lot of trouble probably caused by my inclusion of CxImage for MapFinder.
I don't remember if this was something I needed to do to get it to work.
One thing I added to BULL's makefile right away is to point to the Boost and Python libraries and includes in BTS's folder rather than forcing the modder to copy them to every SDK folder. Windows shortcuts fail us here, but it's easy with this at the top:
I modified your makefile to add a COPYTO macro instead of assuming the DLL will go into an mod's Assets folder and defined a BIN folder to hold fastdep.exe.
However, after all that I cannot get it to work with BULL. BULL includes CxImage (a mix of C and C++ files) stored in subfolders. I have the files appearing in sources.mk, but I can't figure out how to tell it to build the cpp or c files. Here's the file I ended up with:
BULL is used in a few other mods, and it seems most everyone has to remove the CxImage stuff to get it to build. Do you know how I could set up a separate CxImage project so I can build a statically-linked CxImage.lib myself to include with BULL? That way other modders could use BULL out-of-the-box?
Breaking up CyCityInterface.cpp
I got the error about the debugging information overflow with this file, so I checked the compiler settings. Some of the options in your makefile are redundant, and some differ in ways that I'd like to understand further.
You had these extra options:
- General
- /Gy - enable function-level linking
- /Gm- - disable (?) minimal rebuild
- Debug
- /Zi - generate complete debugging information
- /Od - disable optimization
- Release
- /Oy - omit frame pointer
- Oi - generate intrinsic functions
I could only find "/Gm" which enabled minimal rebuild. I assume it's off by default, but the docs didn't list the - option to this feature.
/Zi seems to be what kills CyCityInterface1.cpp. I'm trying other /Z settings but will probably end up splitting the original file as everyone else has. It might be nice to supply a pre-split file.
The main difference (not listed above) however is that I use /MDd for debug builds and link against MSVCPRTD.lib which is supposed to be for debugging. That requires "/NODEFAULTLIB:msvcprtd.lib" in the debug libs. Do you know if this is necessary? It's been a long time since I put together BULL's makefile using the original from Refar, and I had a lot of trouble probably caused by my inclusion of CxImage for MapFinder.
I don't remember if this was something I needed to do to get it to work.One thing I added to BULL's makefile right away is to point to the Boost and Python libraries and includes in BTS's folder rather than forcing the modder to copy them to every SDK folder. Windows shortcuts fail us here, but it's easy with this at the top:
Code:
CIV = C:\Games\Civ4\Beyond the Sword
SDK = $(CIV)\CvGameCoreDLL
BOOST = $(SDK)\Boost-1.32.0
PYTHON = $(SDK)\Python24I modified your makefile to add a COPYTO macro instead of assuming the DLL will go into an mod's Assets folder and defined a BIN folder to hold fastdep.exe.
Code:
BIN = C:\Coding\Civ\SDK\bin
## Uncomment to have newly compiled dlls copied to your mod's Assets directory
COPYTO = $(CIV)\AssetsHowever, after all that I cannot get it to work with BULL. BULL includes CxImage (a mix of C and C++ files) stored in subfolders. I have the files appearing in sources.mk, but I can't figure out how to tell it to build the cpp or c files. Here's the file I ended up with:
Spoiler BULL makefile :
Fimbulvetr
Emperor
Neither /ZI nor /Zi will work with larger source files because of the program database size limit. You will at least want to know the line numbers so you should add /Zd .
Can you get it to work if you just put everything into the $(SDK) folder?
Can you get it to work if you just put everything into the $(SDK) folder?
EmperorFool
Deity
I'll try that one. Really, full debugging info would be great so you could examine variables and expressions. All of the BULL code so far was so straight-forward I didn't need to debug in VS, but this is about more than BULL. Is that the only file that is too large for /Zi?
Probably, but I'm really hoping Danny can help me extract CxImage into a separate static library so no one has to deal with it. You removed it from Better BUG AI, right?
Fimbulvetr
Emperor
No, I didn't remove it, I just had to disable the precompiled headers to get it to work.
But I have never bothered to find out how to use a makefile when I have a vcproj I can compile from, so I never had to fiddle around with obj creation in the makefile.
/Zi vs /Zd: how much more info do you get anyway? I'm glad if I can see the line number.. Anyway I just tried it again and got no errors, both compiler and linker created their pdb files. But I have yet to manage to compile a working dll with /MTd so I'm not sure if that's even relevant.
But I have never bothered to find out how to use a makefile when I have a vcproj I can compile from, so I never had to fiddle around with obj creation in the makefile.
/Zi vs /Zd: how much more info do you get anyway? I'm glad if I can see the line number.. Anyway I just tried it again and got no errors, both compiler and linker created their pdb files. But I have yet to manage to compile a working dll with /MTd so I'm not sure if that's even relevant.
EmperorFool
Deity
/Zi should give you variable and symbol information so you can inspect them while in the debugger and create watch expressions on them: "break if pCity goes NULL".
So you're not using a makefile at all? Do you have the full VC++ 2003 IDE?
So you're not using a makefile at all? Do you have the full VC++ 2003 IDE?
Similar threads
