external modification of a VC++ 6 project
-
Dear ALL!, and Happy New Year 2006! I am writing you from Switzerland and despite the fact that I have been looking in literature about C++ and on line forums, it remains a problem that I would submit to you. I would be grateful of your help. I am far away from being an expert but indeed today ( I mean since days I am blocked by this ! ) I have to manage a project in C++ which is pretty well working and dealing with stocks of the company I work with ( import/export of mineral water and dispatching stocks). My project is within a folder: folder00 [ let's call it so] all *.cpp, *.h files...etc... I have to modify only one *.h file and one *.cpp file. hd01.h blo1.cp ==> for hd01.h, I have to modify line 5 to 22 and replace the block of numbers by a new block of numbers in a worpad file wpd01.rtf ==> same for blo1.cp [line 58 to 72] with wpd02.rtf The path of each file is stable How can I proceed from an external C++ executable file [ let's call it external.cpp]? And how can I automatically rebuilt the project? From external.cpp too? Thanks a lot, Greetings, TPP
-
Dear ALL!, and Happy New Year 2006! I am writing you from Switzerland and despite the fact that I have been looking in literature about C++ and on line forums, it remains a problem that I would submit to you. I would be grateful of your help. I am far away from being an expert but indeed today ( I mean since days I am blocked by this ! ) I have to manage a project in C++ which is pretty well working and dealing with stocks of the company I work with ( import/export of mineral water and dispatching stocks). My project is within a folder: folder00 [ let's call it so] all *.cpp, *.h files...etc... I have to modify only one *.h file and one *.cpp file. hd01.h blo1.cp ==> for hd01.h, I have to modify line 5 to 22 and replace the block of numbers by a new block of numbers in a worpad file wpd01.rtf ==> same for blo1.cp [line 58 to 72] with wpd02.rtf The path of each file is stable How can I proceed from an external C++ executable file [ let's call it external.cpp]? And how can I automatically rebuilt the project? From external.cpp too? Thanks a lot, Greetings, TPP
so basically you just want to build the project from the command line rite? if yes check nmake.exe and how u can use it, you will need to export a makefile from ur project.
-Prakash
-
so basically you just want to build the project from the command line rite? if yes check nmake.exe and how u can use it, you will need to export a makefile from ur project.
-Prakash
Hello, No, in fact there is a project that I can compile, rebuild, link...in Visual C++ 6.0 The name of this project is Proj001 and located in folder \projtpp But it uses a *.h file that I want to update several times a day because it contains new data inside. the problem is: how can I build up a new project ( only based on one *.cpp file) that compile , rebuild and execute automatically Proj001? Thanks a lot, P
-
Hello, No, in fact there is a project that I can compile, rebuild, link...in Visual C++ 6.0 The name of this project is Proj001 and located in folder \projtpp But it uses a *.h file that I want to update several times a day because it contains new data inside. the problem is: how can I build up a new project ( only based on one *.cpp file) that compile , rebuild and execute automatically Proj001? Thanks a lot, P
thierrypp wrote:
I want to update several times a day because it contains new data inside.
:confused: Why store data directly inside of your application? Your app should be getting that data from a data source, a simple flat text file or database would suffice. Doing so would eliminate the need to recompile so often.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
thierrypp wrote:
I want to update several times a day because it contains new data inside.
:confused: Why store data directly inside of your application? Your app should be getting that data from a data source, a simple flat text file or database would suffice. Doing so would eliminate the need to recompile so often.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
Hi, No, in fact it contains secure keys to update frequently. That is why the less I display the best is the security. But let's say, ok I can manually change data within the *h and *cpp file. Then if I have previously built up a makefile called "filesecure" how can I rebuild all until have a new executable file? I am working with Visual C++ 6.0 Best Regards
-
Hi, No, in fact it contains secure keys to update frequently. That is why the less I display the best is the security. But let's say, ok I can manually change data within the *h and *cpp file. Then if I have previously built up a makefile called "filesecure" how can I rebuild all until have a new executable file? I am working with Visual C++ 6.0 Best Regards
Still makes no difference, hiding that data inside of the binary is still no different than hiding it in plain sight. Remember if its human readable even when its in the binary its still human readable. It would much more secure to look at a different approach to your security. Building at the command line is done via nmake, this is the easiest way to do an auto build. MSDN Link Building on the Command Line[^]
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
Hi, No, in fact it contains secure keys to update frequently. That is why the less I display the best is the security. But let's say, ok I can manually change data within the *h and *cpp file. Then if I have previously built up a makefile called "filesecure" how can I rebuild all until have a new executable file? I am working with Visual C++ 6.0 Best Regards
There is an option in VS6 to create make files for you. I dont remember off the top of my head where the option is. But use it to create your first make file. Other wise here is an example from the MSDN. Sample Makefile[^]
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
There is an option in VS6 to create make files for you. I dont remember off the top of my head where the option is. But use it to create your first make file. Other wise here is an example from the MSDN. Sample Makefile[^]
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
Yes I made one called FileSecure.MAK but now from a complete directory, how to manage this from windows XP? On MSDN, it is well explained, thank you, but to be practical..... How to launch this Filesecure.Mak from C:\sptp folder? and my project FileSecure is located in an other path#
-
Yes I made one called FileSecure.MAK but now from a complete directory, how to manage this from windows XP? On MSDN, it is well explained, thank you, but to be practical..... How to launch this Filesecure.Mak from C:\sptp folder? and my project FileSecure is located in an other path#
I'm just guessing here as I have never had to use NMAKE (I just know it’s a tool available and part of VS, there are better Automated building applications out on the internet). You probably have to supply the full qualified path to all of the files within the NMAKE file. Or it looks like there is an option to supply file paths as part of the NMAKE command. Running NMAKE[^] NMAKE Options[^] Running NMAKE is done via the command line; you could even create a batch file with the necessary options / commands to simplify it even further. Lastly I still urge you to consider an alterative to your current security set up, remember that your “key” is still visible in the binary and in the header and is plainly visible to everyone (sorry I just to had to say it)
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.