klauncher and kdeinit on win32 initial running

[Ralf Habacker]

Imre Szabo schrieb:
> Dear Ralph,
>
> Last year  you were kind to me for compiling
> Neuroscope and Klusters to run Cygwin. Recently
> several efforts  has been made for porting KDE, Qt and
> xml in Windows. As I am not able to estimate it, could
> you tell me whether the recent standing of these
> efforts permit compilation the Neuroscope and Klusters
> or we should wait for further progress.
>   
As far as i know is neuroscope based on qt3 and kde 3, which isn't 
available as native windows port.
To compile neuroscope on windows it is required to port to qt4 (may be 
the qt3support module may decrease the required porting effort) and the 
kde related parts to kde4 (here also the kde3support module may help to 
reduce the required porting need)
Third KDE4 uses cmake as buildsystem (http://www.cmake.org) , which 
supports windows and Mac OS/X and cmake support to neuroscope has to be 
added.

As starting point i have append initial cmake buildsystem support, which 
should be places into the neuroscope sources.

Then one can configure and compile with the following commands for the 
win32 gnu cc compiler (MINGW):

    mkdir neuroscope-build
    cd neuroscope-build
    cmake -G "MinGW Makefiles" <neuroscope-source-root-dir>
    mingw32-make

Porting neuroscope could then be started. If you need professional 
assistance in this area or you are looking for someone doing this, send 
me a personal email.

Best regards
Ralf

> Best regards,
>
> Imre
>
> --- Ralf Habacker  wrote:
>
> --- Ralf Habacker <ralf.habacker at freenet.de> wrote:
>
>   
>> Hi all,
>>
>> in the last days there were some efforts to get
>> klauncher and kdeinit on 
>> win32 running.
>>
>> The current state is, that klauncher is able to
>> start win32 applications 
>> with command line parameters (at least on mingw,
>> which I have tested)
>>
>> The recent implementation does not depends on
>> kdeinit like the unix 
>> version, because forking isn't available under
>> windows, any process is 
>> started as regular process even kio slaves. Instead
>> klauncher uses 
>> QProcess to start additional applications inside
>> klauncher. 
>>
>> kdeinit is designed as initial launcher for the
>> basic kde application 
>> like dbus-daemon, klauncher and kded (and optional
>> application like unix 
>> kdeinit does using the +app syntax).
>>
>> My notes to this implemenation are:
>> - The unix version of klauncher/kdeinit uses very
>> much native unix api 
>> function for example socket code. My question is if
>> there are any plans 
>> for a (may be partial) redesign to avoid duplicated
>> parts in the unix 
>> and windows code.
>>
>> Anyone who is interested in seeing KDE on windows is
>> invited to check 
>> and advance this features.
>>
>> Regards
>> Ralf
>>
>>
>>
>>
>> _______________________________________________
>> Kde-windows mailing list
>> Kde-windows at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-windows
>>
>>     
>
>
> Imre Szabó M.D., Ph.D.
> Professor of Neuropsychology,
> Institute of Behavioral Sciences,
> Faculty of Medicine, Pécs University,
> Szigeti u 12.,
> H-7624 Pecs, Hungary
> Tel: +36 72 536-258, Fax: +36 72 536-257,
> mobile: +36  20 204-9128, home:+36 72 312-660
>
>
>  
> ____________________________________________________________________________________
> Cheap talk?
> Check out Yahoo! Messenger's low PC-to-Phone call rates.
> http://voice.yahoo.com
> _______________________________________________
> Kde-windows mailing list
> Kde-windows at kde.org
> https://mail.kde.org/mailman/listinfo/kde-windows
>   

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CMakeLists.txt
Url: http://mail.kde.org/pipermail/kde-windows/attachments/20061125/3efaec3d/attachment.txt