|
[Sponsors] |
Why is wmakelnInclude designed the way it is? |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
July 23, 2016, 13:55 |
Why is wmakelnInclude designed the way it is?
|
#1 |
Member
Join Date: Aug 2015
Posts: 37
Rep Power: 10 |
As far as I can tell,
Code:
EXE_INC = \ $(LIB_SRC)/B/lnInclude \ $(LIB_SRC)/A/lnInclude
Code:
EXE_INC = \ $(LIB_SRC)/B/lnInclude It seems to me that the current system forces the programmer to dive into the dependencies of the modules that (s)he uses, and that this is a task which would be easy to delegate to a script. What's the motivation behind the current approach? |
|
July 26, 2016, 08:54 |
|
#2 |
Senior Member
Gerhard Holzinger
Join Date: Feb 2012
Location: Austria
Posts: 335
Rep Power: 28 |
Here is my take on the build system:
If wmakeLnInclude would work the way you describe in your post, you would generate loads of symlinks. In the current implementation, each module has its own lnInclude folder which contains symlinks to all files belonging to that very module. Thus, if you search for a particular file in your OF sources by name, you find it twice. The file and the symlink. Code:
user@host/OpenFOAM/OpenFOAM-dev/src$ find . -name fvMesh.H ./finiteVolume/lnInclude/fvMesh.H ./finiteVolume/fvMesh/fvMesh.H Furthermore, under the system you proposed, there would be a mix of links to files belonging to the module and links to files belonging to other modules in a module's lnInclude directory. A compiler warning/error pointing to the file moduleA/lnInclude/X.H would then not automatically indicate, that file X of moduleA is at fault. It could also be file X of moduleK. Granted, you would eliminate the need to include many lnInclude entries in the Make/options file, however, under the current system there is a clear division of labour (or knowledge). The lnInclude folder contains all the symlinks to the module's own files. Whereas, Make/options contains all information on the dependencies of a module. |
|
July 26, 2016, 14:10 |
|
#3 |
Member
Join Date: Aug 2015
Posts: 37
Rep Power: 10 |
Good points. I don't think that any of the issues you raise are insurmountable, though:
|
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[DesignModeler] How to create fluid body as I first designed the solid part through solid works? | rasekh64 | ANSYS Meshing & Geometry | 9 | May 13, 2013 14:15 |
Designed with CATIA V5 a 3D re-entry capsule | Ahura | Main CFD Forum | 0 | May 10, 2013 17:28 |
ANSYS User Interface would be Designed by Apple | keerthivasan | ANSYS | 0 | January 31, 2013 09:57 |
analyze a cd nozzle with fluent which designed by MOC | mehrzad | Main CFD Forum | 0 | July 6, 2011 05:33 |
OpenFoam 1.6-ext - error ./Allwmake in /src | preibie | OpenFOAM Installation | 14 | June 14, 2011 06:57 |