Bug 912 - building XKB docs is broken on cygwin
Summary: building XKB docs is broken on cygwin
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Build/Monolithic (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-21 10:57 UTC by Alexander Gottwald
Modified: 2011-10-15 22:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
proposed patch (1.57 KB, patch)
2004-07-21 11:00 UTC, Alexander Gottwald 		no flags Details | Splinter Review
fixed missing tabs (1.57 KB, patch)
2004-07-26 01:18 UTC, Alexander Gottwald 		no flags Details | Splinter Review
Show Obsolete (1) View All

Description Alexander Gottwald 2004-07-21 10:57:56 UTC 
the buildsystem assumes name.ps and name.PS are different files and creates
links or deletes the original files on clean.

The solution is to take CaseSensitveFileSystem as conditional in this case
Comment 1 Alexander Gottwald 2004-07-21 11:00:31 UTC 
Created attachment 507 [details] [review]
proposed patch

Wraps linking of name.ps -> name.PS in an extra define which empty for
CaseSensitiveFileSystem == NO and tests for CaseSensitiveFileSystem before
linking the XKBlib.ps.gz -> XKBlib.PS.gz
Comment 2 Matthieu Herrb 2004-07-25 09:39:35 UTC 
The same problem exists on Mac OS X. The proposed patch seems to work too.
Comment 3 Alexander Gottwald 2004-07-26 01:18:31 UTC 
Created attachment 525 [details] [review]
fixed missing tabs
Comment 4 Alexander Gottwald 2004-07-26 01:25:07 UTC 
/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.117; previous revision: 1.116
/cvs/xorg/xc/config/cf/X11.tmpl,v  <--  X11.tmpl
new revision: 1.18; previous revision: 1.17
/cvs/xorg/xc/doc/hardcopy/XKB/Imakefile,v  <--  Imakefile
new revision: 1.3; previous revision: 1.2

marked as fixed

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.