Michael Gooch | 22 Nov 03:37 2014
Picon

[Bug 341171] New: problems with windows paths in kdevelop

https://bugs.kde.org/show_bug.cgi?id=341171

            Bug ID: 341171
           Summary: problems with windows paths in kdevelop
           Product: kde-windows
           Version: unspecified
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: porting
          Assignee: kde-windows@...
          Reporter: goochmi@...

Could not view contents of windows paths, had problems accessing alternative
drives.

Porting should probably be adjusted so it understands the windows paths that
begin with drive letters, as that seemed to be at least a component of the
problem.

Reproducible: Always

Steps to Reproduce:
1. emerge kdevelop
2. try to create new project or open a location as a project

Actual Results:  
navigating paths doesn't work smoothly, or at all, depending on where you try
(Continue reading)

Paul Manners | 21 Nov 09:13 2014
Picon

Emerge error

Hi


When running "emerge qt" for the first time, I get the following error message:emerge debug: buildAction: all emerge debug: packageName: ['qt'] emerge debug: buildType: RelWithDebInfo emerge debug: buildTests: False ________________________________________________________________________________ ERROR: The system was unable to find the specified registry key or value. 'mt' is not recognized as an internal or external command, operable program or batch file. emerge error: fatal error: package gnuwin32/patch all failed
I've googled for this error and I've looked on the KDE-Windows forums but I haven't found a solution.


Doing a search on my C: I found an application called c:\Program Files (x86)\Windows Kits\8.1\bin\x64\mt.exe.  Should this be in my search path somewhere and how do I specify this?

Thanks
Paul
_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows
Paul Manners | 19 Nov 09:12 2014
Picon

Trouble with setting up KDE build environment

Hi, 

I'm going through the process described here:


to try and get a build environment set up.  

I using VS2013 express running on x64 and Win8. 

My directory structure is:

c:\kderoot\emerge
c:\kderoot\etc\kdesettings.ini

where kdesettings.ini has been copied from the emerge directory and edited accordingly.

I've tried this with the git branches master and kde-4.13 for emerge without success.   I don't have a kdesettings.bat (when using the master branch) following the discussion on this list related to bug #339016.  When running a powershell (powershell -executionpolicy unrestricted), I am able to run the .\kdeevn.ps1 script successfully.  However when it comes to running "emerge --help" it doesn't appear that it is in the application search path.  I've looked at the README docs in the emerge directory but they haven't shed any light.  Given I need to run kdeevn.ps1, I can't run it in my git bash prompt.  Running kdeevnt.bat in git-bash doesn't seem to work either.  

I'm sure this is something silly, perhaps someone can point me in the right direction?

regards
Paul

 
_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows
Michael Gooch | 12 Nov 19:16 2014
Picon

[Bug 340899] New: Konsole package cmake file wants missing framworks package: PTY

https://bugs.kde.org/show_bug.cgi?id=340899

            Bug ID: 340899
           Summary: Konsole package cmake file wants missing framworks
                    package: PTY
           Product: kde-windows
           Version: unspecified
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: porting
          Assignee: kde-windows@...
          Reporter: goochmi@...

After changing CONFIG to MODULE so that the previous error of not having the
master config file for KF5 is sidestepped, one finds that the cmake file wants
the KF5PTY package, which does not appear to exist yet for kde-windows.

Reproducible: Always

Steps to Reproduce:
1. try to emerge konsole

Actual Results:  
failure message about missing KF5PTY cmake files

Expected Results:  
konsole compiles, or at least attempts to, (gets beyond dependency checks)

Might simply be that PTY isn't ready yet, but figured it couldn't hurt to
submit this in a separate bug report, since it is technically a different
issue.

--

-- 
You are receiving this mail because:
You are the assignee for the bug.
Michael Gooch | 10 Nov 22:45 2014
Picon

[Bug 340834] New: emerge konsole error: KF5 missing

https://bugs.kde.org/show_bug.cgi?id=340834

            Bug ID: 340834
           Summary: emerge konsole error: KF5 missing
           Product: kde-windows
           Version: unspecified
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: other
          Assignee: kde-windows@...
          Reporter: goochmi@...

CMake Error at CMakeLists.txt:24 (find_package):
  Could not find a package configuration file provided by "KF5" with any of
  the following names:

    KF5Config.cmake
    kf5-config.cmake

Reproducible: Didn't try

I'm trying to see if I can find a framework or package that supplies the
missing piece, this looks like a missing dependency problem

--

-- 
You are receiving this mail because:
You are the assignee for the bug.
Michael Gooch | 10 Nov 20:37 2014
Picon

[Bug 340831] New: Error on emerge kdevelop in kcwsh

https://bugs.kde.org/show_bug.cgi?id=340831

            Bug ID: 340831
           Summary: Error on emerge kdevelop in kcwsh
           Product: kde-windows
           Version: unspecified
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: other
          Assignee: kde-windows@...
          Reporter: goochmi@...

[ 79%] [ 82%] Building CXX object
tests/CMakeFiles/terminaltest.dir/terminaltest.cpp.obj
Building CXX object
tests/CMakeFiles/terminaltest.dir/terminaltest_automoc.cpp.obj
q:\kcwsh\tests\terminaltest.cpp: In constructor 'TestTerminal::TestTerminal()':
q:\kcwsh\tests\terminaltest.cpp:61:52: error: 'nullptr' was not declared in
this scope
 TestTerminal::TestTerminal() : Terminal(), m_timer(nullptr) {
                                                    ^
q:\kcwsh\tests\terminaltest.cpp: In member function 'void
TestTerminal::startCmdDelayed(std::vector<std::basic_string<wchar_t> >, int)':
q:\kcwsh\tests\terminaltest.cpp:66:19: error: 'nullptr' was not declared in
this scope
     if(m_timer != nullptr) {
                   ^
q:\kcwsh\tests\terminaltest.cpp: In member function 'virtual void
TestTerminal::sizeChanged()':
q:\kcwsh\tests\terminaltest.cpp:138:34: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
                     c = { 80, 25 };
                                  ^
q:\kcwsh\tests\terminaltest.cpp:138:23: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
                     c = { 80, 25 };
                       ^
q:\kcwsh\tests\terminaltest.cpp:140:44: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
                     m_testSize = { 162, 52 };
                                            ^
q:\kcwsh\tests\terminaltest.cpp:140:32: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
                     m_testSize = { 162, 52 };
                                ^
q:\kcwsh\tests\terminaltest.cpp:145:44: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
                     m_testSize = { 160, 50 };
                                            ^
q:\kcwsh\tests\terminaltest.cpp:145:32: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
                     m_testSize = { 160, 50 };
                                ^
q:\kcwsh\tests\terminaltest.cpp:150:49: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
                     m_testSize = { 10000, 10000 }; // we want to restrict to
the maximum size now
                                                 ^
q:\kcwsh\tests\terminaltest.cpp:150:32: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
                     m_testSize = { 10000, 10000 }; // we want to restrict to
the maximum size now
                                ^
q:\kcwsh\tests\terminaltest.cpp: In function 'int main()':
q:\kcwsh\tests\terminaltest.cpp:220:33: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
         t.m_testSize = { 80, 25 };
                                 ^
q:\kcwsh\tests\terminaltest.cpp:220:22: warning: extended initializer lists
only available with -std=c++11 or -std=gnu++11
         t.m_testSize = { 80, 25 };
                      ^
jom:
R:\build\testing\kcwsh\work\mingw-w64-RelWithDebInfo-gitHEAD\tests\CMakeFiles\terminaltest.dir\build.make
[tests\CMakeFiles\terminaltest.dir\terminaltest.cpp.obj] Error 1
jom:
R:\build\testing\kcwsh\work\mingw-w64-RelWithDebInfo-gitHEAD\CMakeFiles\Makefile2
[tests\CMakeFiles\terminaltest.dir\all] Error 2
jom: R:\build\testing\kcwsh\work\mingw-w64-RelWithDebInfo-gitHEAD\Makefile
[all] Error 2
emerge warning: while running make cmd: jom
emerge error: fatal error: package testing/kcwsh all failed

Reproducible: Always

Steps to Reproduce:
emerge konsole

Actual Results:  
error as above

Expected Results:  
proper compilation of dependencies and konsole itself

--

-- 
You are receiving this mail because:
You are the assignee for the bug.
Michael Gooch | 10 Nov 20:31 2014
Picon

[Bug 340829] New: Cryptic Warnings on emerge KDevelop

https://bugs.kde.org/show_bug.cgi?id=340829

            Bug ID: 340829
           Summary: Cryptic Warnings on emerge KDevelop
           Product: kde-windows
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: other
          Assignee: kde-windows@...
          Reporter: goochmi@...

Could not find drkonqi at r://bin/drkonqi
kbuildsycoca5 running...
Recreating ksycoca file ("C:/Users/Michael/AppData/Local/cache/ksycoca5",
version 300)
Menu "applications.menu" not found.
"applications.menu"  not found in  ()

Saving
Emitting notifyDatabaseChanged ("services", "servicetypes", "xdgdata-mime",
"apps")

r:\>emerge kdevelop
emerge debug: buildAction: all
emerge debug: packageName: ['kdevelop']
emerge debug: buildType: RelWithDebInfo
emerge debug: buildTests: False
________________________________________________________________________________
Warning: General/EMERGE_ARCHITECTURE is deprecated and has ben renamed to
General/Architecture

applications menu etc above

Reproducible: Didn't try

Actual Results:  
It seems to have emerged properly, I just don't know what the above means.. Is
it a missing dependency, or something that would trigger if an app menu
existed?

Expected Results:  
No such warnings

the only thing i've explicitly tried to emerge was kdevelop, its entirely
possible that it is searching for something like nautilus or gnome application
lists.

--

-- 
You are receiving this mail because:
You are the assignee for the bug.
Andrius da Costa Ribas | 8 Nov 23:27 2014
Picon

Review Request 121081: QT_WA

This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/121081/

Review request for KDE Base Apps, KDE Frameworks and kdewin.
By Andrius da Costa Ribas.
Repository: kde-baseapps

Description

QT_WA is not available on Qt5. We also only use the Unicode version, anyways.

Testing

It builds (MSVC2013 - 64bit) after this patch (along other patches I'm sending to review today). Kdebase-apps is still not very functional, though (missing icons and weird UI).

Diffs

  • lib/konq/src/konq_copytomenu.cpp (7f97c12)

View Diff

_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows
Andrius da Costa Ribas | 8 Nov 23:26 2014
Picon

Review Request 121080: Replace KDE_DUMMY_QHASH_FUNCTION.

This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/121080/

Review request for KDE Base Apps, KDE Frameworks and kdewin.
By Andrius da Costa Ribas.
Repository: kde-baseapps

Description

Since we're not using kdemacros.h here anymore, KDE_DUMMY_QHASH_FUNCTION is not available. Implement it instead.

Testing

It builds (MSVC2013 - 64bit) after this patch (along other patches I'm sending to review today). Kdebase-apps is still not very functional, though (missing icons and weird UI).

Diffs

  • lib/konq/src/konq_historyentry.h (de34d6b)

View Diff

_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows
Andrius da Costa Ribas | 8 Nov 23:14 2014
Picon

Review Request 121076: Do not require KF5::Su on Windows

This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/121076/

Review request for KDE Frameworks and kdewin.
By Andrius da Costa Ribas.
Repository: kde-baseapps

Description

kdepasswd, which requires it, is already disabled on Windows. There is also konq-plugins/shellcmdplugins which was also disabled on Windows, but konq-plugins is entirely disabled now.

Testing

It builds (MSVC2013 - 64bit) after this patch (along other patches I'm sending to review today). Kdebase-apps is still not very functional, though (missing icons and weird UI).

Diffs

  • CMakeLists.txt (f02b069)

View Diff

_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows
Paul Manners | 8 Nov 20:29 2014
Picon

Building latest release of KDE

Good day, 

I'm wanting to try out the latest version of Okular in Windows.  I've spent some time reading though the documentation on the KDE for Windows Initiative site as well the okular website, forums, IRC and mailing lists.  I'm trying to find a path of least resistance but the details I've found are from posts and documentation that goes back quite some time, so I'm not sure if they are still valid.

My findings so far are: 

- There's no new release of KDE for Windows that includes the latest version of Okular.  The last release was May 2013 based KDE 4.10.2.  I get the feeling that the KDE binary builds (for windows) are no longer being produced due to a shift towards kf5.  I don't however see any formal releases of kf5 so I'm guessing what I need to focus on is a custom build of KDE 4.14.2 in windows.

- With doing a build in Windows, the key thing to me seems to be the choice of build system: either MSVC or MinGW.  I don't see any theoretical reason why the latest version of VS (2013) would not work, but from my research one would definitely not want to go with anything earlier than VS2008  Use of the emerge tool seems to be the way to go.  I'm familiar with GNU tool chain, but was not able to find out whether the MS or GNU route has fewer issues.  I have a requirement for OS X too (so would expect to use GNU), but that's dependent on whether I can test Okular on Windows.

Any pointers or validation of my current assessment of the situation would be greatly appreciated.

Thanks
Paul
_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows

Gmane