| RE: [cdt-dev] MSVC Support Plans |
|
Just FYI that I’ve
got the dependency tracking for the Internal Builder implemented in my
workspace based upon Doug’s PDOM Dependency Calculator. I’m going to check in
the dependency tracking later this week after I do all the necessary testing. Mikhail From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer Actually, I’m using
the build integration I’ve written to build the native code for the
Window debug integration I’m working on next. I’ve been able to
construct the necessary environment variables by poking around in the registry.
I’m using the internal builder instead of nmake, since makefile
generators are not easy things to build. I’m just waiting for the
dependency analysis based on the index to get put in so that the internal
builder will build when header files change and such. Then I’ll release
it for testing. We’re getting closer… Thanks! Doug Schaefer From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Stan Mitchell This might be useful for
unmanaged SDK builds… I ran across an include
file, “Win32.mak”, that supplies common settings for NMAKE
projects. It has been part of the
Platform SDK going back to the Windows 95 days. Many of the MS Makefiles In the Windows SDK it can
be found at “Microsoft SDKs\Windows\v6.0\Include\Win32.mak”. Regards, SourceQuest, Inc. From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer Very cool, thanks to
pointing me at the Window SDK. When I saw it the first time, I thought it was
for For build integration, I
currently still rely on gnu make so that I can reuse the code that generates
gnu makefiles. To keep things simple, this is the wrong way to go. At the end
of the day, I want to use our internal builder so that I don’t have to
generate a makefile at all. This will probably be the right solution for 4.0,
once we get dependency handling in place. In the meantime, I think I’ll
target nmake. I’ll also look at vcbuild, which might be a great solution
for people migrating from VisualStudio to Eclipse. I’ll send an update
when I get something together. From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Hi Doug, Great!
Perhaps I can help with testing. I tried an
install of the .NET 2.0 SDK. The C/C++ compiler/link/lib versions match those
in Visual Studio 2005. However, the include directory is pretty sparse. You
might augment it with the Platform SDK which has header files for Win32, etc.
All of these different SDKs are merging into a single “Windows SDK”
(free download) which is at release-candidate-1 stage now. Visual Studio also
includes source for C runtime, C++ standard lib, and MFC (I’m not sure if
those will be available in the Windows SDK). Are you using
vcbuild.exe along with the vcproj xml file format for encoding project contents
and tool chain options? Or are you
leveraging the GNU make code by using nmake or another make variant? Regards, SourceQuest,
Inc. From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer Funny you
should mention this. I have the MSVC MBS definitions almost ready to go.
They’ll be under the guise of C++.Net but should also work for other
versions of MSVC. It will be distributed in a separate component release
hopefully within a few weeks. From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Hi all, I’m curious if MSVC
MBS support is something that is planned for CDT 3.x/4. Doug Schaefer’s
design notes at http://wiki.eclipse.org/index.php/CDT/designs/msvc
suggest that it is at least under consideration. Thanks, SourceQuest, Inc. |