U++ forum: Welcome to the forum

A couple of requests to help importing source libraries [message #35087]

Wed, 11 January 2012 00:51

mdelfede
Messages: 1307
Registered: September 2007

Ultimate Contributor

I have an huge library (OpenCascade, as usual...) which has a quite weird folder structure and build process.
I'd like to have it imported into some Upp packages,but WITHOUT touching at original source tree, because I'd like to submit patches for it and doing it on a modified source tree is cumbersome and time consuming.
So, the problem : OCC (or better, OCE, the community edition) structure is the following (in short) :

OCE
  inc      containing some thousands of include files
  src      containing package separated hand written source files
  drv      containing packages separated auto generated src files

besides the inc folder, which contains tons of include without subfolder, the tree is arranged in a weird way; for instance, even if the library is divided in

MODULES
  |
    TOOLKITS
      |
         PACKAGES

the structure of src folder, for example is

src/PACKAGENAME/sourcefiles

My solution would be to add an 'uppoce' subfolder inside OCE main folder, with just a tree of upp packages referencing the real sources; en example .upp file :

noblitz;

options
	-I../../../../inc,
	-I../../../../src/Dynamic,
	-I../../../../drv/Dynamic;
file
	../../../../src/Dynamic/Dynamic_AbstractVariableInstance.cxx,
	../../../../src/Dynamic/Dynamic_BooleanParameter.cxx,
.......

Problem n.1 : upp don't allow ../../ paths in .upp files. Well, it allows them but don't compile, just preprocessing and 'show assembly' works. In Linux I can solve with symlinks of source files in package folder, but it's not portable to windows; windows has some kind of symlinks, but they're hard to use or works only on Vista+ OS.
As I'd like to ask maintainers of OCE to include an UPPOCE folder, the only viable solution would be the one I put in sample .upp file above.

Problem n.2 : I could 'translate' OCE library using a relationship of :
PACKAGE---> PACKAGE; that would bring some 2-300 upp packages...
TOOLKIT---> PACKAGE; that would bring some 56 upp packages
MODULE ---> PACKAGE, that would bring just 4-5 upp packages, but could arise in inter-dependencies problems.

The best solution would be the first, then grouping with 'super upp packages' up to module level; so :
about 300 upp packages for OCE packages
plus about 56 upp packages for OCE toolkits, grouping the former 300
plus 5-6 upp packages for modules, grouping all above.

The problem is that when opening the 'add package' dialog you'd be prompted with some 400 packages coming from OCE, mixed with upp and own ones, which is unmanageable.
The nicest solution would be to add an 'HIDE SUBPACKAGES' checkbox on upp, or add an 'hidden flag' on .upp packages and a flag "show/hide hidden packages" inside theide, which, btw, could be useful to reduce the number of presented packages.

Resuming, I'd like to have :

1) Relative paths in .upp files ("../../somefolder/somefile")
2) A way to hide on demand some packages from theide

is all that feasible ?

Max

Report message to a moderator