Closed Bug 114644 Opened 23 years ago Closed 23 years ago

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

Categories

(Calendar :: Internal Components, defect)

Product:
Calendar
Component:
Internal Components
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: gray, Assigned: gray)

Details

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.
This is John's.
Assignee: mikep → gray
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
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
Closed: 23 years ago
Resolution: --- → FIXED
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
Can somebody verify this.  I'm not sure what to look for.
Keywords: verifyme
Verified
Status: RESOLVED → VERIFIED
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
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.