> On Jan 29, 2015, at 10:07 PM, Carel Combrink <[email protected]> wrote: > > Hi, > > With my SpellChecker Plugin a few comments were received about trying to > integrate the plugin into the main QtCreator code (upstreaming it). > > Regarding this I would like to know: Say I get the code to conform to the > QtCreator coding standard, how would I handle the external dependencies of > the plugin? At the moment the plugin depends on the Hunspell spellchecker > library to do the actual spell checking. For this it needs the headers as > well as the library to build and link the plugin. > > On Linux this is not such a big issue, but on Windows it can be a bit more > problematic. > > Any help in this regard will be appreciated.
As a first step you could do it the way it is done for the clang code model plugin: The user can set a (environment) variable to point the build to the library and its headers + there is a fallback that tries to find the library from the system. If that is successful, the plugin is built. Br, Eike > PS: I have just created a new release that now also checks String Literals. > > Regards, > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller, Senior Software Engineer - The Qt Company GmbH The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
