Title: | Microsoft Visual C++ bug reports and kits |
Notice: | Register in Topic 2. 5.Last for latest Kit |
Moderator: | DECWET::THOMAS N |
Created: | Tue May 17 1994 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 521 |
Total number of notes: | 2938 |
Hi all, A software partner of ours is just finishing a port from UNIX (a variety of platforms) to Windows NT. They want to provide their software on Intel and on Alpha, and I am supporting them on Alpha. They have a major problem with Microsoft Developer Studio makefiles. It concerns consistency between project configurations for different platforms. You can only change a configuration for the machine you are working on. Whenever you change the list of include directories, preprocessor definitions, linker input files, ... on one platform, you must open the project again on the other platform in order to apply the same changes there. This problem could be solved by a tool which takes a set of parameters and generates MSDEV makefiles automatically. Does anyone know of any such tool? Most probably all our software partners have the same problem, don't they? I would be very grateful for any suggestions! Heidrun. - Crossposted in PARTNER_EXCELLENCE - ___________________________________________________________________________ Heidrun Baumert Tel: +49 (89) 9591 2356 --------------- DTN: *865 2356 Software Partner Enginnering FAX: <ditto> 2220 Digital Equipment GmbH Easynet: alfam7::baumert Munich, Germany. @RTO Internet: [email protected] ___________________________________________________________________________
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
453.1 | DECWET::KOWALSKI | Time's not for saving | Wed Jan 29 1997 08:05 | 14 | |
Since they have already produced this product on UNIX, why don't they simply use their UNIX makefiles on NT? It's then a matter of finding a make facility on NT which is compatible with their makefiles and isolating the platform dependencies in the makefiles. Since the makefiles will be shared between all the platforms, they'll have a much more portable application and a lot less maintainence. (and yes, it can be done: my product shares makefiles and 1500 source modules between various UNIXes and NT). Mark | |||||
453.2 | EDSCLU::NICHOLS | Wed Jan 29 1997 09:56 | 16 | ||
If your makefiles dont do anything too strenuous, nmake will probably get you by. It will do "if $()" so you can check for platform and appropriately set compiler/link exe names and flags. One thing it does not do which some unix makes will is recursively expand macros until nothing expands further. It might also be possible to wrap the makefile inside a vc generated one. Look at using "Makefile Projects". All your unix stuff stays in place, but is called from the vc environment. Good Luck, roger | |||||
453.3 | don't use IDE .mak files for joint alpha/x86 development | DECWET::PETERSON | Wed Mar 05 1997 16:10 | 6 | |
VC V5 will be better at maintaining separate targets in an IDE project. until then, there is no good way to coordinate development on both Intel and Alpha platforms using IDE project files. I would treat makefiles as you do under Unix, and use IDE projects that just wrap the makefile. |