Subject: RE: [sv-cc] Update on inclusion doc
From: Warmke, Doug (doug_warmke@mentorg.com)
Date: Mon Feb 10 2003 - 22:46:24 PST
Michael,
Thanks a lot for doing all this work.
I think parts 1 and 2 are good and are pretty
much ready for inclusion into the LRM.
Is the "excerpt from an internal document" that last
attachment regarding the potential IP directory structure?
Francoise,
In our face-to-face, you mentioned that you had a lot of
experience with the complexities of supporting a source-based
C/C++ code inclusion system. It would be great to see some
"Francoise questions and issues" mail on this topic. We could
all learn from your experience.
Thanks and regards,
Doug
> -----Original Message-----
> From: Michael Rohleder [mailto:michael.rohleder@motorola.com]
> Sent: Wednesday, February 05, 2003 8:49 AM
> To: SystemVerilog CC DWG
> Subject: [sv-cc] Update on inclusion doc
> Importance: High
>
>
> Hi all,
>
> as proposed here is the update on the SW inclusion document. Updates:
> - Removed env var features, as requested by the team (all parts)
> - Describes the intention, as requested by the team (intro)
> - Shows some of the possible use case to give some reasons
> for the amount of flexibility needed (intro)
> - Makes the actual switch names no longer mandatory, but
> recommended, as requested by Francoise (intro)
> (if EDA vendors want to use this to distinguish them from
> others, fine with me ...)
> - Current working directory is default, if no -sv_root
> switch given (intro)
> - Permits now only shared libraries (archives are no longer
> possible), as requested by Francoise. (part1)
> - Clarified on the responsibility to provide correct on
> complete data (part1), requested by Doug
> - Added a recommendation on how to handle unreferenced code
> (part1), requested by myself
> - Fixed some errors in the examples
> - Part 2 is mostly unchanged
> - Part 3 is now added for DISCUSSION PURPOSES _only_. Just
> want to find out what the team thinks about it. You tasked me
> to do this, now tell me whether it is O.K. to pursue this
> direction or shut it down ...
>
> Open question from my side:
> - My hope is intro & part 1) is now mostly O.K. ?
> - Do we want to continue with part 2)
> - Only issue left with part 2) is how to handle 'generated'
> header files included in a simulation
> - Is part 3) something we want (I will show some problems in
> the conf call) or should we just kill it.
>
> Remaining things left:
> - Inclusion of .o stuff as requested by Andrzej ->
> since Francoise had some _very_ good points to remove .a,
> I _hope_ this is no longer required ...
> - Definition of associations with C source and VL code as
> requested by Andrzej ->
> I am still VERY hesitant to do this. This would be open up
> a can of worms ...
> But I have added some excerpt from an internal document
> that shows how this could be done as requested in the
> previous call. I had to remove a lot to not exhibit internal
> information, but I think you get the scheme ...
>
> Best regards,
> Michael
>
>
>
>
> --
>
> NOTE: The content of this message may contain personal views
> which are not neccessarily the views of Motorola,
> unless specifically stated.
>
> ___________________________________________________
> | |
> _ | Michael Rohleder Tel: +49-89-92103-259 | _
> / )| Software Technologist Fax: +49-89-92103-680 |( \
> / / | Motorola, Semiconductor Products, System Design | \ \
> _( (_ | _ Schatzbogen 7, D-81829 Munich, Germany _ | _) )_
> (((\ \>|_/ > < \_|</ /)))
> (\\\\ \_/ / mailto:Michael.Rohleder@motorola.com \ \_/ ////)
> \ /_______________________________________________\ /
> \ _/ \_ /
> / / \ \
>
> The information contained in this email has been classified
> as: Motorola General Business Information (x)
> Motorola Internal Use Only ( )
> Motorola Confidential Proprietary ( )
>
>
> *** This note may contain Motorola Confidential Proprietary or
> Motorola Internal Use Only Information and is intended to be
> reviewed by only the individual or organization named above.
> If you are not the intended recipient or an authorized
> representative
> of the intended recipient, you are hereby notified that
> any review,
> dissemination or copying of this email and its
> attachments, if any,
> or the information contained herein is prohibited. If you
> have received
> this email in error, please immediately notify the sender by
> return email and delete this email from your system.
> Thank you! ***
>
>
This archive was generated by hypermail 2b28 : Mon Feb 10 2003 - 22:46:54 PST