Carlo | 1 Jul 2009 10:03
Picon
Gravatar

Re: KCalc v2.4 (using KDE v4.2.3) on Windows Vista crashes due to Access Violations

On Wed, Jul 1, 2009 at 9:06 AM, Brolin Empey<brolin <at> brolin.be> wrote:
> Hello,
>
> I used the KDE Windows installer in end-user mode to install the MSVC
> build of KCalc v2.4 (using KDE v4.2.3) on Windows Vista Ultimate
> Edition SP1 i386.  KCalc runs, but is unusable because it keeps
> crashing with Access Violation exceptions.  On the first section of
> the “Settings” menu, I can enable everything except for Logic Buttons,
> which causes an Access Violation when I try to enable it.  I thought I
> could still use KCalc as long as I do not try to enable Logic Buttons,
> but I cannot even add 2 integers:  KCalc crashes with an Access
> Violation exception when I either press the ‘+’ key on my keyboard or
> click the ‘+’ button on the KCalc window!
>
> How can I make KCalc stable?  I like KCalc because, unlike the Windows
> Calculator, it supports editing the bits of a number.
>
> Thanks,
> Brolin
>
> --
> Sometimes I forget how to do small talk: <http://xkcd.com/222/>
>
> “What if there were no hypothetical questions?” — George Carlin
> _______________________________________________
> Kde-windows mailing list
> Kde-windows <at> kde.org
> https://mail.kde.org/mailman/listinfo/kde-windows
>

(Continue reading)

Brolin Empey | 1 Jul 2009 18:02
Picon
Favicon

Re: KCalc v2.4 (using KDE v4.2.3) on Windows Vista crashes due to Access Violations

2009/7/1 Carlo <brandon.ml@...>:
> it's a known bug and it has been fixed already, unfortunately right
> now you have two options, either wait for the next release or you can
> build it yourself

That is good to know.  I will wait for the next release.
Brent Stephens | 2 Jul 2009 01:37
Picon
Favicon

Re: Kile on windows

Works now.  Had to set PATH appropriately, and there was another small issue with quotation marks which has now been fixed in the latest svn, but not in the latest stable.


Thanks guys.

On Tue, Jun 30, 2009 at 5:59 PM, Brent Stephens <bnstephe-GZvvpLG7cYSVc3sceRu5cw@public.gmane.org> wrote:
Yes, it appears that Rob Bayer has been working on this.  Thanks, I'll check with the folks over there.


On Tue, Jun 30, 2009 at 4:58 PM, Diego <panda84 <at> inwind.it> wrote:
Brent Stephens ha scritto:

I'm trying to get Kile working on windows.  As far as I have been able to tell, no one has really given it much time before.

Try to contact Rob Bayer:
http://sourceforge.net/mailarchive/forum.php?thread_name=178194f0903111922n28d54de5n8fed516efa103428%40mail.gmail.com&forum_name=kile-devel
http://sourceforge.net/mailarchive/forum.php?thread_name=178194f0903151332x391edb2bo516088236406722d%40mail.gmail.com&forum_name=kile-devel

Kile-devel mailing list should know better what's the status of Kile under Windows.


_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows
Patrick Spendrin | 2 Jul 2009 02:27
Picon
Picon

Re: Kile on windows

Brent Stephens schrieb:
> Works now.  Had to set PATH appropriately, and there was another small
> issue with quotation marks which has now been fixed in the latest svn,
> but not in the latest stable.
Does this mean it makes sense to provide a new binary for kile together
with 4.3rc1? If yes I will put it on the list besides koffice and kdevelop.
> 
> Thanks guys.
regards,
Patrick
Rob Bayer | 2 Jul 2009 08:48
Picon

Re: Kile on windows

On Wed, Jul 1, 2009 at 5:27 PM, Patrick Spendrin <ps_ml-Mmb7MZpHnFY@public.gmane.org> wrote:

Does this mean it makes sense to provide a new binary for kile together
with 4.3rc1? If yes I will put it on the list besides koffice and kdevelop.




Most definitely.  I don't the Kile binary has been updated since I made all the Windows compatibility fixes a few months ago, so it's probably due.

Rob
_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows
Patrick Spendrin | 3 Jul 2009 15:34
Picon
Picon

www/sites/windows

SVN commit 990897 by sengels:

add release notes for 4.3rc1 release
CCMAIL:kde-windows <at> kde.org

 M  +23 -0     news.rdf  

--- trunk/www/sites/windows/news.rdf #990896:990897
 <at>  <at>  -11,6 +11,29  <at>  <at> 
 <copyright>Copyright (c) 2007-2009 windows.kde.org Webmaster</copyright>
 <item>
 <title>
+   First release candidate of KDE 4.3 for Windows available
+</title>
+<date>
+   July  2nd, 2009
+</date>
+<fullstory>
+The KDE on Windows team today announced the immediate availability of the first release candidate for the upcoming
+4.3 release series.
+This release also provides some snapshots of unstable applications: Konsole, Yakuake, Kile, KDevelop, Konversation.
+Also a part of the 2.0.1 release of KOffice has been included.
+Please be aware that some of these applications might not be available in the upcoming stable releases though.
+As a test for the upcoming 4.3 release, the two packages kdesdk and kdegraphics have been split up into
single 
+application packages. These can be installed separately.
+The binary packages could be installed with the installer by using the version "unstable 4.2.95" (or
"unstable latest"). 
+In case you are upgrading your KDE installation, deselect the skip basic settings checkbox on the first
installer page 
+and press next until you are guided to the release settings page where you can choose the required version.
+<br/>
+(<i><a href="mailto:kde-windows[AT]kde[DOT]org">KDE on Windows Team</a></i>)
+
+</fullstory>
+</item>
+<item>
+<title>
    KDE 4.2.2 for Windows available
 </title>
 <date>

Chris Morgan | 4 Jul 2009 08:06
Picon

KDE for Windows, Portable Edition

Hi!  I'm a developer from PortableApps.com, and I've taken an interest in KDE for Windows, and specifically in making it portable.


I've had some ideas, some of which I've discussed in #kde-windows, and others which I have just pondered.  To start with, I'll briefly overview the important details of the PortableApps.com Format.  Everything belongs in what by default is X:\PortableApps\KDEPortable (but it can be anything).  Another way some things can be done is shared libraries in e.g. X:\PortabelApps\CommonFiles\KDE, (e.g. Java), however I don't think this is the best way of doing it with KDE (feel free to correct me, I don't know terribly much about the framework). Inside the KDEPortable directory, you'd have App\KDE, being what would normally be C:\Program Files\KDE.  Data gets stored in KDEPortable\Data.  I was told in #kde-windows that changing the environment variable KDEHOME should redirect all data, which is very convenient (otherwise it'd be very difficult to do it all).

It seems to me that the easiest way of doing it would be the following:
  1. Have a modified version of the package manager/installer, which overrides the installation directory to App\KDE, and cleans up the installation files so that nothing is left behind on the host machine (putting them on the USB drive would be too slow, but you can't just leave them behind in TEMP).  Also, rather than registering executables in the start menu, put them into some format which the KDE Portable launcher can find.
  2. KDE Portable launcher: due to the lack of the start menu, we'd need a KDE app launcher.  This could be responsible for changing KDEHOME, or an ordinary NSIS launcher could do it.  I could do this in AutoHotkey easily enough, but I reckon that a C++/Qt one would be better for consistency; I think it'd be better overall if you did it all, with me for advice on the PortableApps.com side of things.  I think a ListView/QListView-based system would be best and easiest, but you're the experts.
Naming: would you prefer it to be called KDE for Windows, Portable Edition, KDE Portable, KDE for Windows Portable, or something else?  I'm guessing KDE for Windows, Portable Edition.  FYI, Mozilla apps we've got Portable Editions of because of Mozilla licensing restrictions, everything else is just Portable.  But if the whole product name is KDE for Windows, adding Portable Edition may be better than just Portable.

I hope I've made sense, and you can understand what I'm wanting and suggesting.  What do you think?


Thanks,

Chris Morgan <chris.morganiser-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


I don't need a quote in my signature.  It's hard enough surviving as it is without having to find a meaningful quote.  Will you forgive me?  Or don't you read this bit?
_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows
sanyaade | 5 Jul 2009 01:59
Picon
Favicon

Re: KDE for Windows, Portable Edition

Hi Chris,
 
Having read your email and having being a user of most of the PortableApps kits on Windows. Also being a Lecturer. Many of my students have been enjoying PortableApps as it removes many of the headaches that needs administrative priveledges on many Windows like Win2000, XP and Vista. Experiences show that KDE should be setup and configured like the OpenOffice Portable Edition. Why? KDE environment is a platform in its own right for running many applications that are based on it. Just like OpenOffice has Writer, Calc, Draw, etc.., and also package Java jre along, KDE environment is also a framework and runtime kit, so if we can follow and learn from the experience of that of an already working environment like OpenOffice Portable Edition will make it a song worth singing.
 
Combating Security issues and continous (almost everyday) updates of Windows O/S has turn most Windows families into hostile environments that are breaking many previous installed/working applications and rendering them useless. This is major headache and many people, organisations are fighting how to turn off Windows Automatic Updates --> We need to be aware of this. Everything that belongs to KDE for Windows Portable Edition should in it's own very folder and no other folder like temp, documents and setting...., etc... Also it will be good to avoid long folder names as Windows applications break down if folder names/level is getting between 120 to 180 or more. More also every Windows layout have different profile for their users since Microsoft is still finding or still running around an established layout/profile.
 
Portable means Portable which is the essence of  why we need the Portable edition of KDE for Windows. The size of KDE could grow from 300MB to 3GB or more but must be portable and run from USB PenDrive/Flash Drive, CDROM, DVD, Portable USB HDD, etc.. Having a KDE for Windows Portable Edition will be a dream come true for me and my students and many other users out there. Keep it up and make it happen.  Cheers!!!
 
 
God blesses!!!
 
Best regards,
Sanyaade
----- Original Message -----
Sent: Saturday, July 04, 2009 7:06 AM
Subject: KDE for Windows, Portable Edition

Hi!  I'm a developer from PortableApps.com, and I've taken an interest in KDE for Windows, and specifically in making it portable.

I've had some ideas, some of which I've discussed in #kde-windows, and others which I have just pondered.  To start with, I'll briefly overview the important details of the PortableApps.com Format.  Everything belongs in what by default is X:\PortableApps\KDEPortable (but it can be anything).  Another way some things can be done is shared libraries in e.g. X:\PortabelApps\CommonFiles\KDE, (e.g. Java), however I don't think this is the best way of doing it with KDE (feel free to correct me, I don't know terribly much about the framework). Inside the KDEPortable directory, you'd have App\KDE, being what would normally be C:\Program Files\KDE.  Data gets stored in KDEPortable\Data.  I was told in #kde-windows that changing the environment variable KDEHOME should redirect all data, which is very convenient (otherwise it'd be very difficult to do it all).

It seems to me that the easiest way of doing it would be the following:
  1. Have a modified version of the package manager/installer, which overrides the installation directory to App\KDE, and cleans up the installation files so that nothing is left behind on the host machine (putting them on the USB drive would be too slow, but you can't just leave them behind in TEMP).  Also, rather than registering executables in the start menu, put them into some format which the KDE Portable launcher can find.
  2. KDE Portable launcher: due to the lack of the start menu, we'd need a KDE app launcher.  This could be responsible for changing KDEHOME, or an ordinary NSIS launcher could do it.  I could do this in AutoHotkey easily enough, but I reckon that a C++/Qt one would be better for consistency; I think it'd be better overall if you did it all, with me for advice on the PortableApps.com side of things.  I think a ListView/QListView-based system would be best and easiest, but you're the experts.
Naming: would you prefer it to be called KDE for Windows, Portable Edition, KDE Portable, KDE for Windows Portable, or something else?  I'm guessing KDE for Windows, Portable Edition.  FYI, Mozilla apps we've got Portable Editions of because of Mozilla licensing restrictions, everything else is just Portable.  But if the whole product name is KDE for Windows, adding Portable Edition may be better than just Portable.

I hope I've made sense, and you can understand what I'm wanting and suggesting.  What do you think?


Thanks,

Chris Morgan <chris.morganiser-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


I don't need a quote in my signature.  It's hard enough surviving as it is without having to find a meaningful quote.  Will you forgive me?  Or don't you read this bit?

_______________________________________________
Kde-windows mailing list
Kde-windows-RoXCvvDuEio@public.gmane.org
https://mail.kde.org/mailman/listinfo/kde-windows
_______________________________________________
Kde-windows mailing list
Kde-windows@...
https://mail.kde.org/mailman/listinfo/kde-windows
Alexander Neundorf | 5 Jul 2009 18:23
Picon
Favicon

KDE4 on cygwin, was: Re: KDE/kdelibs/cmake/modules

On Saturday 04 July 2009, Ralf Habacker wrote:
> Alexander Neundorf schrieb:
> > On Thursday 02 July 2009, Ralf Habacker wrote:
> >> SVN commit 990260 by habacker:
> >>
> >> Account for CMAKE_EXECUTABLE_SUFFIX in KDE4_*_EXECUTABLE .shell names,
> >> since that is how they are created. by cygwin ports maintainer
> >
> > cygwin ?
>
> yes
>
> > Is anybody trying to build KDE4 for cygwin ?
>
> see
> http://sourceforge.net/mailarchive/message.php?msg_name=4A40846D.4000607%40
>users.sourceforge.net and
> http://sourceforge.net/mailarchive/message.php?msg_name=cfbb9574d343e573421
>fa69acebef295%40email.freenet.de for more details.
> It would be nice, if someone with detailed cmake know how could help him.

Can you please ask him to join the kde-buildsystem mailing list ?

Is this part of the patch really correct ?

--- origsrc/kdelibs-4.2.4/cmake/modules/KDE4Macros.cmake
+++ src/kdelibs-4.2.4/cmake/modules/KDE4Macros.cmake
 <at>  <at>  -567,6 +569,8  <at>  <at>  macro (KDE4_ADD_PLUGIN _target_NAME _wit

    if (_first_SRC)
       set_target_properties(${_target_NAME} PROPERTIES PREFIX "")
+   else (_first_SRC)
+      set_target_properties(${_target_NAME} PROPERTIES PREFIX "lib")
    endif (_first_SRC)

    if (WIN32)

---------------

This patch is inside the following macro:
macro (KDE4_ADD_PLUGIN _target_NAME _with_PREFIX)
#is the first argument is "WITH_PREFIX" then keep the standard "lib" prefix, 
otherwise set the prefix empty

I.e. the old version removed the default "lib" prefix on UNIX systems by 
default. If WITH_PREFIX was used, it did not remove the "lib" prefix on UNIX 
systems, but also on Windows systems it did not add a "lib" prefix. 
With the patch it seems to add a "lib" prefix, also on Windows, also for MSVC.

Do we want that ?

Also, the patch doesn't seem to be complete, since there is still the 
following code in FindKDE4Internal.cmake:

if (WIN32)
   if(CYGWIN)
      message(FATAL_ERROR "Cygwin is NOT supported, use mingw or MSVC to build 
KDE4.")
   endif(CYGWIN)

Alex
Yaakov (Cygwin/X | 5 Jul 2009 23:58
Picon
Gravatar

Re: KDE4 on cygwin, was: Re: KDE/kdelibs/cmake/modules

On 05/07/2009 11:23, Alexander Neundorf wrote:
> Is anybody trying to build KDE4 for cygwin ?

Yes, me.  When habacker and the kde-cygwin group changed focus to the 
native Win32 port of Qt/KDE, I began providing Qt3.3/KDE3.5 packages 
through my Cygwin Ports project.  With an upcoming major update to 
Cygwin, I'm now working on KDE4 packages as well.

I have most modules, save kdebase-workspace, built and running; e.g. 
here's Konqueror 4.2:

https://sourceforge.net/project/screenshots.php?group_id=99645

Right now I'm submitting patches for kdelibs to bugzilla:

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

I plan to post patches for other modules which need (some build 
completely OOTB) after 4.3.

> Is this part of the patch really correct ?
>
> --- origsrc/kdelibs-4.2.4/cmake/modules/KDE4Macros.cmake
> +++ src/kdelibs-4.2.4/cmake/modules/KDE4Macros.cmake
>  <at>  <at>  -567,6 +569,8  <at>  <at>  macro (KDE4_ADD_PLUGIN _target_NAME _wit
>
>      if (_first_SRC)
>         set_target_properties(${_target_NAME} PROPERTIES PREFIX "")
> +   else (_first_SRC)
> +      set_target_properties(${_target_NAME} PROPERTIES PREFIX "lib")
>      endif (_first_SRC)
>
>      if (WIN32)
>
> ---------------
>
> This patch is inside the following macro:
> macro (KDE4_ADD_PLUGIN _target_NAME _with_PREFIX)
> #is the first argument is "WITH_PREFIX" then keep the standard "lib" prefix,
> otherwise set the prefix empty
>
> I.e. the old version removed the default "lib" prefix on UNIX systems by
> default. If WITH_PREFIX was used, it did not remove the "lib" prefix on UNIX
> systems, but also on Windows systems it did not add a "lib" prefix.
> With the patch it seems to add a "lib" prefix, also on Windows, also for MSVC.
>
> Do we want that ?

Does CMake use an empty CMAKE_SHARED_MODULE_PREFIX on MSVC?

It's up to Ralf then; if that negatively effects him, then a if(NOT 
WIN32) should be added inside the else(_first_SRC).

> if (WIN32)
>     if(CYGWIN)
>        message(FATAL_ERROR "Cygwin is NOT supported, use mingw or MSVC to build
> KDE4.")
>     endif(CYGWIN)

I am working on pushing several patches into Cygwin's cmake (and, 
hopefully, upstream) to make CMake behave correctly on Cygwin; one of 
those patches removes the WIN32 define on Cygwin, since many packages 
(including, but not only, KDE) use WIN32 for (in Qt parlance) 
Q_OS_WIN/Q_WS_WIN, where Cygwin is Q_OS_{CYGWIN,UNIX}/Q_WS_X11.

So yes, if someone tries to build KDE4 with a cmake which defines WIN32, 
it is certainly not supported and the error is justified (although the 
message could be changed to say that only the combination of 
Cygwin/WIN32 is not supported, but Cygwin/X11 is.)

Yaakov
Cygwin Ports

Gmane