Building KDevelop master with craft on Windows failing

Morten Volden mvolden2 at gmail.com
Thu Nov 22 10:04:45 GMT 2018


Hi Kevin

Thanks - Much appreciated.

I am now able to build KDevelop in Debug mode. Curiously, I am not able to
start it though.

The executable is there, but when I type kdevelop in the craft terminal
nothing happens.

I am, however, able to execute the unittests from within the terminal and
that was what I wanted in the first place. Will try to investigate that
issue when time permits.

Cheers,



Den tir. 20. nov. 2018 kl. 13.40 skrev Kevin Funk <kfunk at kde.org>:

> On Monday, 19 November 2018 19:23:08 CET Morten Volden wrote:
> > Hi All
> >
> > I have done a craft --destroy-craft-root to try and build from a clean
> root
> > directory.
>
> That will not destroy/reset the Git checkouts iirc.
>
> Could you try `git reset --hard` in the kdevelop-pg-qt dir and continue
> with
> craft?
>
> Regards,
> Kevin
>
> > However, I am still experiencing problems with building master branch of
> > KDevelop in Debug mode on Windows.
> >
> > More specific, kdev-pg-qt build fails:
> >
> > FAILED:
> > kdev-pg/CMakeFiles/kdev-pg-qt.dir/kdev-pg-default-visitor-gen.cpp.obj
> >
> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1414~1.264\bin\Hostx64\x64\
> > cl.exe /nologo /TP -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS
> > -DQT_DISABLE_DEPRECATED_B EFORE=0x050400 -DQT_NO_URL_CAST_FROM_STRING
> > -DQT_STL
> > -DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS -DUNICODE
> > -DWIN32_LEAN_AND_MEAN -DWINVER=0x0600 -D_
> > CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_DEPRECATE
> > -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_WARNINGS -D_UNICODE
> > -D_USE_MATH_DEFINES -D_WIN32_IE=0x0600 -D_WIN
> > 32_WINNT=0x0600 -Ikdev-pg
> > -IC:\CraftRoot\download\git\extragear\kdevelop-pg-qt\kdev-pg
> > -Ikdev-pg\kdev-pg-qt_autogen\include -IC:\CraftRoot\download\git\extragea
> > r\kdevelop-pg-qt\include -IC:\CraftRoot\include\qt5
> > -IC:\CraftRoot\include\qt5\QtCore -IC:\CraftRoot\.\mkspecs\win32-msvc
> > /DWIN32 /D_WINDOWS /W3 /GR /EHsc /wd42
> > 50 /wd4251 /wd4396 /wd4661 -EHsc /MDd /Zi /Ob0 /Od /RTC1 /showIncludes
> > /Fokdev-pg\CMakeFiles\kdev-pg-qt.dir\kdev-pg-default-visitor-gen.cpp.obj
> > /Fdkdev-pg\CMake
> > Files\kdev-pg-qt.dir\ /FS -c
> >
> C:\CraftRoot\download\git\extragear\kdevelop-pg-qt\kdev-pg\kdev-pg-default-v
> > isitor-gen.cpp
> >
> C:\CraftRoot\download\git\extragear\kdevelop-pg-qt\kdev-pg\kdev-pg-default-
> > visitor-gen.cpp(22): fatal error C1083: Cannot open include file:
> > 'kdev-pg-default-vi
> > sitor-gen.h': No such file or directory
> >
> > So it cannot find a .h file that I know is part of kdev-pg-qt. This had
> me
> > confused for a while, until I noticed this line further up in the build
> > process:
> >
> > executing command: C:\CraftRoot\dev-utils\bin\git.exe checkout 2.1
> > Already on '2.1'
> > D       kdev-pg/kdev-pg-default-visitor-gen.h
> > Your branch is up to date with 'origin/2.1'.
> > Already up to date.
> > executing command: C:\CraftRoot\dev-utils\bin\git.exe checkout 2.1
> > Already on '2.1'
> > D       kdev-pg/kdev-pg-default-visitor-gen.h
> > Your branch is up to date with 'origin/2.1'.
> > *** Action: unpack for extragear/kdevelop-pg-qt ***
> >
> > So this seems like something within craft is deliberately deleting the .h
> > file. However, it is not super clear to me what that something is.
> Looking
> > through the different python, text, and json files I was not able to spot
> > anything.
> >
> > Also, in the BlueprintSettings.ini file I have specified that I want the
> > master version. Like so:
> >
> > [extragear/kdevelop-pg-qt]
> > version = master
> >
> > But that does not seem to have any effect on the version that is chosen
> for
> > the build (2.1)
> >
> > Any pointer(s) as to what I might be doing wrong would be much
> appreciated.
>
>
> --
> Kevin Funk | kfunk at kde.org | http://kfunk.org



-- 
Regards / Med venlig hilsen

Morten Danielsen Volden
Software Developer
M.Sc. EE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-windows/attachments/20181122/d3415972/attachment-0001.html>


More information about the Kde-windows mailing list