Thought I'd put this to the mailing list for others' benefit. I am trying to interest an "old timer" IC design guy (older than me) in moving from an ancient tool to XCircuit. He immediately brought up questions about how to configure / manage a project to start neatly, consistently.
------------------------------------------------------------------------------------------------------------------------------------------------- I am reading Tutorial 3, Managing Large Projects, as it looks to lay out the init file and some project management rules. However it's obviously Linux-centric, calling out system variables, which are difficult to deal with in Windows (or at least, totally obscure and unfamiliar to me, and the paradigm of how you start stuff is totally different, no xterm invocation because who uses a terminal window in Windows?). I would appreciate any guidance about how best to set up multiple projects (for multiple chip designs) on a Windows PC. Do we need to (say) create an icon with "Start In" and maybe a modified command (proper "dash options", etc.) under the icon properties? Or make a batch file that can jam the right "shell variables" (Windows style, whatever they may be) before invoking XCircuit, and iconify -that-? I am looking to make something where I can double-click on a project icon and spawn XCircuit good-to-go, all libs and whatever hooked up... -and- be able to subsequently click another project icon, after quitting out of the first, and have all dependencies changed to -that- project's particulars (no residual cruft like some critical variable stuck with the old project's value). Note that I am not hard-over on any particular implementation,I'd like to stay with "what's normal" if there is such a thing, I knew what it was, and it's capable of what I am after (being able to jump around between projects without getting tangled up -I am familiar with one tools set that stores "some stuff"in the Windows Registry, and makes a mess when you go from a project with Technology A to one that uses Technology B, unless you exit in a very particular way, one which then requires you to manually re-set-up the library path list next time by hand (because the purging just -had- to step on that too). It looks like the example .xcircuitrc files I have pulled, are good for library setup if the searchPath is set up. But that,I think, could use some guidance for the Windows folks.I think back to my Cadence years and how the cshrc file in the project home would set many variables and paths, everything needed, all in one place (but of course this was SunOS and later Linux, which is not helping). But it's a model, if only I had a grip on the "what do I need to do -before- .xcircuitrc is read, given that I insist to use Windows (Linux is "someday", Windows is "now"), to make it so?". Also, I have not yet found a clear list of all of the XCOps() variables' names and functions, I see 4-5 called out in the .xcircuitrc examples but expect there are more, and I might care about some of them? ------------------------------------------------------------------------------------------------------------------------------------------------- J. W. Swonger, President UltraSemi LLC (321) 636-2655 office (321) 458-0472 mobile _______________________________________________ Xcircuit-dev mailing list Xcircuit-dev@opencircuitdesign.com http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
