From: Wheeler, F. (Research) <wh...@cr...> - 2002-11-12 15:26:34
|
> > As to the best directory structure, I think it would be > > easier (for the > > documentation robots, as well as ourselves) if each of > > contributed modules > > stayed at the same relative directory level. So maybe have > > > > /src /vcl > > /vxl > > /v3p > > /contrib/gel > > /rpl > > /mul > > > > I second this. I think the src directory makes core vxl > a lot less scary on first sight. The top level CmakeLists.txt file is currently in /src. With this directory structure we'll have to choose one of these: 1. Put commands like this in the top level CmakeLists.txt SUBDIRS( ../contrib/mul ) but I seem to recall that cmake only allows SUBDIRS that are actually subdirectories. 2. Move the top level CMakeLists.txt file to /src/.. (one up from /src). This will add another layer to the whole tree. My 2 cents: Personally, I think gel/rpl/mul are fine where they are. The idea that vcl/vxl/v3p constiture core-vxl, and that the other dirs are optional can be explained in a README. If VXL is intimidating to someone because 12 of its 324 directories are at the top level, then it will still be intimidating to that person when only 6 of its 325 directories are at the top level. Fred Wheeler |
From: Andrew F. <aw...@ro...> - 2002-11-12 17:18:03
|
I see your point. In fact, inserting src gives us this hierarchy > > > /src /vcl > > > /vxl/vbl > > > /vxl/vil > > > /vxl/vnl > > > /v3p > > > /contrib/gel > > > /rpl > > > /mul > > > So here's a radical suggestion: rename the vxl subdir src, giving > > > /contrib/gel > > > /rpl > > > /mul > > > /src /vbl > > > /vil > > > /vnl > > > /vcl > > > /v3p This gets us out of the old "vxl/vxl" paths which I always thought looked silly. |
From: Ian S. <ian...@st...> - 2002-11-12 17:21:45
|
This would force everyone to write their own root CMakeLists.txt file > -----Original Message----- > From: Andrew Fitzgibbon [mailto:aw...@ro...] > Sent: Tuesday, November 12, 2002 5:18 PM > To: 'Wheeler, Fred (Research)'; 'Vxl-maintainers (E-mail)' > Subject: RE: [Vxl-maintainers] Re: contrib directory > > > > I see your point. In fact, inserting src gives us this hierarchy > > > > > /src /vcl > > > > /vxl/vbl > > > > /vxl/vil > > > > /vxl/vnl > > > > /v3p > > > > /contrib/gel > > > > /rpl > > > > /mul > > > > > > So here's a radical suggestion: rename the vxl subdir src, giving > > > > > /contrib/gel > > > > /rpl > > > > /mul > > > > /src /vbl > > > > /vil > > > > /vnl > > > > /vcl > > > > /v3p > > This gets us out of the old "vxl/vxl" paths which I always > thought looked silly. > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > To learn the basics of securing your web site with SSL, > click here to get a FREE TRIAL of a Thawte Server Certificate: > http://www.gothawte.com/rd522.html > _______________________________________________ > Vxl-maintainers mailing list > Vxl...@li... > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > |
From: Ian S. <ian...@st...> - 2002-11-12 17:29:57
|
> From: Andrew Fitzgibbon > So here's a radical suggestion: rename the vxl subdir src, giving > > > > > /contrib/gel > > > > /rpl > > > > /mul > > > > /src /vbl > > > > /vil > > > > /vnl > > > > /vcl > > > > /v3p > This would force everyone to write their own root CMakeLists.txt file - my own suggestion had the same flaw. > This gets us out of the old "vxl/vxl" paths which I always > thought looked silly. At the expense of no longer calling the collection of Vision-somthing-libraries "VXL" :-) There is another possiblity: Use Amitha's original suggestion. /src/vcl /v3p /vxl /contrib/oxl /rpl /mul Those robots (i.e. our documentation builders) which need a consistent two layer module/library scheme can use a special entry in the CVSROOT/Modules files to do it for them. Ian. |
From: Peter V. <Pet...@es...> - 2002-11-12 17:30:32
|
> So here's a radical suggestion: rename the vxl subdir src, giving > > /contrib/gel > /rpl > /mul > /src /vbl > /vil > /vnl > /vcl > /v3p I must say that I like this proposal. -- Peter. |
From: Ian S. <ian...@st...> - 2002-11-12 17:54:13
|
> 1. Put commands like this in the top level CmakeLists.txt > SUBDIRS( ../contrib/mul ) > but I seem to recall that cmake only allows SUBDIRS that are > actually subdirectories. I've just tested this. It sort of works, but not well enough to be useful. The main problem is that CMake appears to put the binaries for mul into ../contrib/mul, rather than ../bin as I specified. |