Re: [wxCode-users] Re: Building wxCode components

[Otto W. <ott...@or...>]

Mike Wetherell wrote:
> 
> So what I'd suggest is that, instead of using these environment
> variables, the components be put directly into the wxWidgets tree
> rather than linked.
> 
> So for example, a CVS user would checkout wxCode then move the
> 'components' subdirectly into wxWidgets/contrib. I believe that cvs
> would still work correctly for the moved components subdirectory, and
> also when using cvs for wxWidgets, it would ignore the wxCode stuff.
> 
I don't like to copy but you are free to to do what you want. It might
be possible to checkout directly into wxWidgets/contrib but I think
WinCVS won't be able to separate wxWidgets and wxCode projects. On
Windows you probably have to make sure you don't copy the CVS directories.

> The reason I suggest this is that:
> 1. wxWidgets' bakefiles can be run 'as is' to generate makefiles for
> wxCode if we do this.
> 2. Not all filesystem have links.
> 3. Not all make programs support variables (though I guess those ones
> could be avoided).
> 
It would be nice to have Backfile generate all the make files. So best
if you make a description (understandable by a user) how to handle it
correctly, then anyone can decide for himself if he wants to copy. I'll
put your description on the wxCode web page.

> What do you think?
> 
I prefer wxWidgets/contrib/components/... . As much as I understand this
doesn't need any changes in wxCode. 

BTW how far did you come with moving everything to gzstreams?

Otti

-- 
See a huge pile of work at "http://wyodesktop.sourceforge.net/"