After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 112776 - Support for Visual Studio .NET 2003
Support for Visual Studio .NET 2003
Status: RESOLVED FIXED
Product: libsigc++
Classification: Bindings
Component: build
1.2
Other Windows
: Normal normal
: ---
Assigned To: Martin Schulze
Martin Schulze
Depends on:
Blocks:
 
 
Reported: 2003-05-11 17:51 UTC by burrisj
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch for adding support for Visual Studio .NET 2003 compiler (1.78 KB, patch)
2003-05-11 17:53 UTC, burrisj
none Details | Review
Visual Studio .NET 2003 project files (4.44 KB, application/octet-stream)
2003-05-11 17:56 UTC, burrisj
  Details
New Project files (18.57 KB, application/octet-stream)
2003-05-13 02:28 UTC, burrisj
  Details

Description burrisj 2003-05-11 17:51:47 UTC
Add support and project files for the Visual Studio .NET 2003 compilier
Comment 1 burrisj 2003-05-11 17:53:46 UTC
Created attachment 16430 [details] [review]
Patch for adding support for Visual Studio .NET 2003 compiler
Comment 2 burrisj 2003-05-11 17:56:25 UTC
Created attachment 16431 [details]
Visual Studio .NET 2003 project files
Comment 3 Murray Cumming 2003-05-12 13:08:06 UTC
Reassigning to libsigc++, because that's what the patch seems to be for.
Comment 4 Murray Cumming 2003-05-12 13:29:11 UTC
Please give me a filename for the Visual Studio project file. I would
like to put this in a release in the next few days.
Comment 5 Murray Cumming 2003-05-12 16:08:48 UTC
Note that the project filename should probably be called
MSVC/libsigc++_msvcX.something, next to the exising
MSVC/libsigc++_msvc6.dsp. I guess the X would be 8 (if that's what
they call it) or Net2003 or something.

Please check that works.
Comment 6 burrisj 2003-05-13 02:28:15 UTC
Created attachment 16476 [details]
New Project files
Comment 7 Murray Cumming 2003-05-13 15:14:45 UTC
Please tell us what that attachment is. For instance, please give us a
filename.
Comment 8 burrisj 2003-05-14 01:54:48 UTC
The attached zip file contains the following project files:

libsigc++_mscvNet2003.vcproj
libsigc++_msvcNet2003.sln
README.msvcNet2003
tests/   
tests/bind_return_test/
tests/bind_return_test/bind_return_test.vcproj
tests/bind_test/
tests/bind_test/tests/bind_test/
tests/class_slot_test/class_slot_test.vcproj
tests/connection_test/
tests/connection_test/connection_test.vcproj
tests/hide_test/
tests/hide_test/hide_test.vcproj
tests/method_slot_test/
tests/method_slot_test/method_slot_test.vcproj
tests/object_slot_test/
tests/object_slot_test/object_slot_test.vcproj
tests/object_test/
tests/object_test/object_test.vcproj
tests/retype_return_test/
tests/retype_return_test/retype_return_test.vcproj
tests/retype_test/
tests/retype_test/retype_test.vcproj
tests/size_test/
tests/size_test/size_test.vcproj
tests/slot_test/
tests/slot_test/slot_test.vcproj

These project files allow the building of debug and release versions 
of ligsigc++ and all test cases.

I hope this helps.

John Burris
Comment 9 Murray Cumming 2003-05-14 05:31:50 UTC
Thanks. I am trying to add this stuff, but:

1.
The README tells people to read a README that doesn't exist.

2.
Why does the main .vcproj also need a .sln, but the test .vcproj files
don't.

3.
Why are the .vproj files in subdirectories? These subdirectories don't
exist yet.
Comment 10 Murray Cumming 2003-05-14 06:04:55 UTC
I've rearranged things a bit. I'll release a new tarball and you can
tell me if it works. If not, I'll release another.
Comment 11 burrisj 2003-05-15 02:40:09 UTC
The .sln file is used to load all the projects into one workspace.  
This is the same as .dsw files in Visual Studio 6.0.  Thie .vcproj 
files will only load that single project onto the workspace.   This 
is the same as *.dsp file in Visual Studio 6.0.  Each .vcproj files 
are in there own directory because Visual Studio automatical creates 
the directories /Debug and /Release in the same directory as 
the .vcproj files.  Therefore, it's very ugly and nearly imposible to 
get Visual Studio to function properly if ever .vcproj file were in 
the same directory.  If you move things around I may be able to get 
it to work, but I make no guarantees.
Comment 12 Murray Cumming 2003-05-16 13:16:53 UTC
So, I think I've done what you wanted. Please try the 1.2.5 release
and tell me if anything needs fixing.
Comment 13 Murray Cumming 2003-05-19 16:15:40 UTC
By the way, the gtkmm changes are waiting until I hear whether this
one worked.
Comment 14 burrisj 2003-05-20 03:30:16 UTC
In the tarball I brought down, there are two new directories MSVC and 
MSVC_NET2003.  Both have the new project files in them.  Which one 
will you be keeping?  MSVC_NET2003 is the same what I gave you and 
will work just fine.  MSVC has changed a little bit and would need a 
few small changes to get them to work.  Let me know if you will be 
adding MSVC to CVS and I will make the required changes.
Comment 15 Murray Cumming 2003-05-20 06:06:51 UTC
Hmm. There should be an MSVC_6 directory, and the MSVC directory 
should be removed. I'll check. Thanks.
Comment 16 Murray Cumming 2003-05-21 06:27:18 UTC
Fixed. Thanks.