>> It's foreign source, and quite large, so please don't >> upload it to Harbour SVN. >> >> I'd suggest to post build instructions inside contrib/hbide/qscintilla >> directory and if a wrapper class is needed add it >> to contrib/hbide/hbqscintilla. >> > > As hbide counterpart, it is not enough. > It has to go inside main stream if I makeup my mind to > exploit it in hbIDE.
QScintilla has not much to do with mainstream Harbour, very big (about 10% of all Harbour codebase, 5MB), and it's not our job to maintain foreign code plus locally maintained build solutions for them. You can also consider moving HBIDE to a separate repository, in which case there is no problem with whatever solution. > Anyway, I posted as you referenced it, and if it is not > appropriate to be a part of hbQT, we can live with the > way I am going through currently. Pls don't convey that there is no other way. We use lots of components in Harbour which we don't host the source code for. Of course if we run out of adequate solution, we're not forced to use Qscintilla inside Harbour. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
