Need to store autogen'd files for platforms that can't autogen

VERIFIED FIXED

Status

VERIFIED FIXED
17 years ago
10 years ago

People

(Reporter: gray, Assigned: gray)

Tracking

Details

(Assignee)

Description

17 years ago
I don't think the libical folks ever came to a definitive decision on how to
handle autogenerated src on platforms that can't generate it.  Perhaps we can
just create a subdirectory, something like autogenex (examples of latest
autogenerated files), and have the build system for platforms that can't build
these files just copy them up from the subdir.  Then I'll periodically check out
the latest, build on a linux box, move copies into the subdir, and then check
them in.

Comment 1

17 years ago
This is John's.
Assignee: mikep → gray

Updated

17 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Assignee)

Updated

17 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 2

17 years ago
the aujogen'd files are now cached in sub-dirs named autogenex off the directory
the autogen'd live in.  

The win32 build system needs to either copy these files up, or generate them.

Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 3

16 years ago
Default QA Contact for Calendar has changed.  If you wish to remain the QA
contact for this bug, feel free to change it back.
QA Contact: colint → brantgurganus2001

Comment 4

16 years ago
Can somebody verify this.  I'm not sure what to look for.
Keywords: verifyme

Comment 5

16 years ago
Verified
Status: RESOLVED → VERIFIED

Updated

13 years ago
QA Contact: gurganbl → libical
Component: libical → Internal Components
The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!
QA Contact: libical → base

Updated

10 years ago
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.