Viktor Szakáts wrote:
>
> Maybe the only generic way to integrate such needs with
> hbmk2, is to create an separate external tool (non-hbmk2)
> and call it as part of of 'preprocessing'. So what needs
> to be done in hbmk2 is to allow to run external tools at
> specific stages of the process, f.e. 'preflight',
> 'postflight', 'prelink'.
>
> I hope to hear ideas on the specifics of such
> implementation.
>
Sounds good. But I am at a loss to understand what type of
tool it could be. You have embedded moc_ creation in Harbour
build system nicely, rather very nicely.
> Though until this is implemented I'd suggest to do the
> 'moc' creation as part of the generator tool.
>
I will think but probably it is not possible due the fact
that at the time of generation the path_to_headers is not
known neither cared. It will increase the complexity IMO.
>> -incpath=${QT_WITH_SCINTILLA}/qt // where QScintilla headers
>> are
>
> In the context of Harbour, QT_WITH_SCINTILLA
> should be named HB_WITH_QSCINTILLA.
>
HB_WITH_QSCINTILLA seems more appropriate, I will change.
>> hbqtgen.prg is tuned to spread sources in the folder its
>> <Class> Folder = qscintilla </Class> section defines.
>
> The clean solution would be to store QSCINTILLA
> related sources inside another .qtp file, instead
> of adding more to the existing qt45.qtp file.
> Pls make it that way. Then the generator can parse
> all existing .qtp files, so there is no change in
> usage.
>
This will be nice. I will try.
> Another (maybe obvious) rule is to strictly avoid
> any qscintilla references in HBQT generated sources.
>
Probably this is the most difficult part and probably not viable.
hbqt_par_Q* - hbqt.h
These must have to go inside hbqt.h otherwise we will end up
replication because the other members are referenced from within
all external lib wrappers anyway. i.e., QFont, QColor, etc.
extern QT_G_FUNC( hbqt_gcRelease_Q* ) - hbqt_garbage.cpp
extern void * hbqt_gcAllocate_Q*l( void * pObj, bool bNew ) -
hbqt_garbage.cpp
These can be somehow isolated in local file like
hbqt_garbage_qscintilla.cpp.
Other implementation could be to create a composite file clubbing _par_
and _gcAllocate_, _gcRelease_ together in the local folder.
I will think over.
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://harbour-devel.1590103.n2.nabble.com/hbMK2-Feature-Request-Auto-generated-moc-cpp-files-tp5089535p5091116.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
