Issue 18647 - OUT2INC operates with possible ambiguities
Summary: OUT2INC operates with possible ambiguities
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: PC All
: P4 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: hjs
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-25 18:20 UTC by philipp.lohmann
Modified: 2004-03-10 16:33 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description philipp.lohmann 2003-08-25 18:20:10 UTC 
In a module several tarballs can be unpacked/build. so far so good, but if one
uses the OUT2INC target to promote built headers to the system dependent output
tree the headers of different tarballs are all delivered to the same directory
possibly creating conflicts. Since such a package tends to have a prefic
directory anyway it would be goot if OUT2INC prefixed its output directory also
to avoid possible conflicts
Comment 1 hjs 2003-08-26 15:34:59 UTC 
introduced OUT2INC_SUBDIR to separate header from different tarballs
in one module
Comment 2 hjs 2004-03-10 16:33:01 UTC 
.