Hi Pritpal,
Viktor Szakáts wrote:
HBQT became very large. We shall split it to multiple libs as
shortly discussed it recently. Best would be to split it along
the QT .dll structure:
/contrib/hbqt/qtcore
/contrib/hbqt/qtgui
/contrib/hbqt/qtnetwork
/contrib/hbqt/qtwebkit
Can you provide a skeleton how to call the make system
for above to implement, under contrib/hbqt folder ?
Or we have to have four folders under contrib/hbqt/hbqtcore , hbqtgui,
hbqtnetwork, hbqtwebkit ?
Yes, exactly.
It will be a little bit similar to rddsql dir layout.
So that I tweak the generator to this effect.
These would remain as is:
/contrib/hbqt/doc
/contrib/hbqt/qth
/contrib/hbqt/tests
/contrib/hbqt/generator
Depends.
You can separate doc and qth, but for simplicity
and to avoid large amount of redundancy the generator
itself should be kept central. The tests as well.
Alternatively we can start hacking make files (msvc and mingw),
but I'd think this isn't the right solution in this case.
Best if this can be achieved.
It's huge job to do generically, doing it partially
would be a hbqt specific hack, which isn't a good idea
as it will block porting hbqt to new compilers.
One suggession would be if we can separate .cpp lib and .prg lib.
That would be making separate libs based on such internal technical
detail as source code kind. This is meaningless for users, and
it takes almost the same amount and type of work as described
in first point. Plus it's fatal if the two becomes unsynced.
So my vote against this.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
