Well Kdevelop and Kdevplatform 4.90.92 build on cygwin.

Kevin Funk kfunk at kde.org
Thu May 19 14:38:09 BST 2016


On Thursday, May 19, 2016 9:32:19 AM CEST Michael George Hart wrote:
> I figured out the unknowable reason; the splash screen was blocking the
> view of the dialog box with the message about QT_PLUGIN_PATH

Hehe, nice.

Another reason for getting rid off the splash screen :)

Glad you figured it out!

Cheers,
Kevin
 
> On May 18, 2016 3:33 PM, "Michael George Hart" <
> 
> michael.george.hart at gmail.com> wrote:
> > For some unknowable I am now getting a dialog with the following message:
> >       "Now I get the error dialog box:
> > Could not find any plugins during startup.
> > Please make sure QT_PLUGIN_PATH is set correctly.
> > Refer to this article for more information."
> > 
> > To tell the truth, after reading the article and  doing some research via
> 
> Google.  setting QT_PLUGIN_PATH does not seem that obvious in the Cygwin
> environment.
> 
> > The source of the shared memory problem can be found in the main.cpp file
> > kdevelop-5/4.90.92/kdevelop-4.90.92/app/main.cph
> > 
> > See code above is the source of my grief under Cygwin ---Years ago coding
> 
> similar to a known kdevelop bug (https://bugs.kde.org/show_bug.cgi?id=249107
> )
> 
> > Intrestingly when I commented out line the lines
> > "if
> 
> (!QProcessEnvironment::systemEnvironment().contains("KDEV_DISABLE_SPLASH"))
> {
> 
> >         splash = new KDevSplashScreen;
> >         splash->show();
> >     
> >     }"
> > 
> > I started getting the Dialog box; now it always appears even when below
> 
> lines of code are uncomment
> 
> >     KDevSplashScreen* splash = nullptr;
> >     if
> 
> (!QProcessEnvironment::systemEnvironment().contains("KDEV_DISABLE_SPLASH"))
> {
> 
> >         splash = new KDevSplashScreen;
> >         splash->show();
> >     
> >     }
> >     
> >     if(!Core::initialize(splash, Core::Default, session))
> >     
> >         return 5;
> > 
> > I read KCrash::initialize does no do anything when in debug mode. Where
> 
> can I get the source code to this so I may try the latest build under
> cygwin?
> 
> > I have tracked down that QXcbShmImage: shmget() failed (88) for size
> 
> 179960 (409x110) may have something to do with how xserver is started on MS
> WINDOWS
> 
> > Anything you guys want me to try
> > 
> > On May 18, 2016 4:56 AM, "René J.V." <rjvbertin at gmail.com> wrote:
> >> On Tuesday May 17 2016 16:13:13 Michael George Hart wrote:
> >> >Unfortunately proceeding to run it stopped at the 10% splash screen,
> >> >showing on the command line
> >> >$ kdevelop
> >> >Fontconfig error: "/etc/fonts/conf.d/66-google-noto-nastaliq-urdu.conf",
> >> >line 35: mismatched tag
> >> >QXcbShmImage: shmget() failed (88) for size 179960 (409x110)
> >> 
> >> I'm not sure that's related. What do other Qt5 applications show (if
> 
> they run), like Qt's Assistant for instance?
> 
> >> If they too get stuck on this or a comparable error, the 1st thing to
> 
> try would be to move aside all .conf files from etc/fonts/conf.d .
> 
> >> FWIW, I'm also seeing QXcbShmImage smget errors when I use the XCB qpa
> 
> plugin on OS X, but they're apparently benign.
> 
> >> And that brings me to the 64k$ question: is it expected that Qt5/KF5
> 
> applications use X11 under Cygwin, rather than some native display engine
> (QPA)?
> 
> >> R.


-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20160519/a05f4f5b/attachment.sig>


More information about the KDevelop mailing list