<table><tr><td style="">habacker added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D5175" rel="noreferrer">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D5175#181288" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;" rel="noreferrer">D5175#181288</a>, <a href="https://phabricator.kde.org/p/bcooksley/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;" rel="noreferrer">@bcooksley</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>I still question how these installs conflict - as all the scenarios where they could conflict should already be taken into account:</p>
<ol class="remarkup-list">
<li class="remarkup-list-item">Linux distros, FreeBSD, etc have no co-installability issues here</li>
<li class="remarkup-list-item">Windows installs should be one prefix per application, which means KF5 and KDE 4 installs should never collide</li>
<li class="remarkup-list-item">macOS is basically the same as Windows, only difference being it's a .app bundle instead
<br /><br />
Can you provide some background please Ralf?</li>
</ol></div>
</blockquote>
<p>see below</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Note that the CI already has native Umbrello builds for Windows so cross compilation shouldn't be required.</p></blockquote>
<p>Relating to the jenkins based system: How can I check build internals in case of hidden build issues ? From my 16 year porting KDE experience (<a href="https://en.wikipedia.org/wiki/KDE_on_Cygwin" class="remarkup-link" target="_blank" rel="noreferrer">https://en.wikipedia.org/wiki/KDE_on_Cygwin</a>) - because of the number of related packages, build systems and possible configuration - this is required often and could not be provided by a build log. You need to inspect for example cmake generated files like include_cxx.rsp which contains the used include directories (a real world example is <a href="https://phabricator.kde.org/D9404" class="remarkup-link" target="_blank" rel="noreferrer">https://phabricator.kde.org/D9404</a>)</p>
<p>Therefore I'm using obs build service. After installing osc (<a href="https://en.opensuse.org/openSUSE:OSC" class="remarkup-link" target="_blank" rel="noreferrer">https://en.opensuse.org/openSUSE:OSC</a>) on a linux machine, I run</p>
<div class="remarkup-code-block" style="margin: 12px 0;" data-code-lang="text" data-sigil="remarkup-code-block"><pre class="remarkup-code" style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; padding: 12px; margin: 0; background: rgba(71, 87, 120, 0.08);">osc co home:rhabacker:branches:windows:mingw:win32:KF541/mingw32-kio
cd home:rhabacker:branches:windows:mingw:win32:KF541/mingw32-kio
osc build</pre></div>
<p>In case of errors I run</p>
<p>osc chroot</p>
<p>to enter the chrooted build environment</p>
<p>to enter package source dir I enter</p>
<div class="remarkup-code-block" style="margin: 12px 0;" data-code-lang="text" data-sigil="remarkup-code-block"><pre class="remarkup-code" style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; padding: 12px; margin: 0; background: rgba(71, 87, 120, 0.08);">cd /home/abuild/rpmbuild/BUILD/kio-5.41.0</pre></div>
<p>to enter package source dir I use</p>
<div class="remarkup-code-block" style="margin: 12px 0;" data-code-lang="text" data-sigil="remarkup-code-block"><pre class="remarkup-code" style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; padding: 12px; margin: 0; background: rgba(71, 87, 120, 0.08);">cd /home/abuild/rpmbuild/BUILD/kio-5.41.0/build</pre></div>
<p>to continue broken build I run</p>
<div class="remarkup-code-block" style="margin: 12px 0;" data-code-lang="text" data-sigil="remarkup-code-block"><pre class="remarkup-code" style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; padding: 12px; margin: 0; background: rgba(71, 87, 120, 0.08);">cd /home/abuild/rpmbuild/BUILD/kio-5.41.0/build
make</pre></div>
<p>I can edit files, clean builds, restart build, make patches to fix issues in build system and so one</p>
<p>Doe KDE CI provide shell access to the complete build infrastructure like installed 3rdparty packages, source and build files ?</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R241 KIO</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D5175" rel="noreferrer">https://phabricator.kde.org/D5175</a></div></div><br /><div><strong>To: </strong>habacker, dfaure, ltoscano, bcooksley<br /><strong>Cc: </strong>cgiboudeaux, Frameworks<br /></div>