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 496722 - DSP/DSW files in win32/vs6 directory are in unix format
DSP/DSW files in win32/vs6 directory are in unix format
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Windows
: Normal normal
: 0.10.15
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-14 12:31 UTC by Julien MOUTTE
Modified: 2007-12-17 23:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (635 bytes, patch)
2007-11-14 21:52 UTC, David Schleef
committed Details | Review

Description Julien MOUTTE 2007-11-14 12:31:54 UTC
Visual C++ 6.0 will not open those files if they don't use DOS format. autotools should somehow make sure those files are disted in the right format.
Comment 1 Jan Schmidt 2007-11-14 12:40:43 UTC
It would be good if someone that knows how to do dist-hooks could give us a snippet that either checks and warns or automatically converts the win32/vs6/*.ds[pw] files to DOS line endings.
Comment 2 David Schleef 2007-11-14 21:52:48 UTC
Created attachment 99114 [details] [review]
patch

Here's how to do it.  I didn't contemplate too long whether this is the most maintainer-friendly method.
Comment 3 Jan Schmidt 2007-11-15 17:43:52 UTC
Unmarking this one as a blocker, because I've fixed it manually for this release.
Comment 4 Tim-Philipp Müller 2007-12-17 23:42:27 UTC
This is fixed for core and base in CVS now:

 2007-12-17  Tim-Philipp Müller  <tim at centricular dot net>

        * win32.mak: (win32), (win32defs), (win32crlf):
          Make check for CR LF in Visual C++ 6.0 project files
          work, based on patch by David Schleef (#496722, #393626).

Theres bug #393626 about the same issue, so closing this and keeping the other one open until it's fixed in all modules.