This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Developeing with KDE4 on windows

Tags: None
(comma "," separated)
User avatar
CourtJesterG
Registered Member
Posts
3
Karma
0

Developeing with KDE4 on windows

Mon Dec 01, 2008 2:09 am
Yes i been following the instructions provided here:

http://techbase.kde.org/Getting_Started ... troduction

I so far got to Running emerge section and get stuck!

C:
cd %KDEROOT%emerge
Then you have to execute

kdeenv.bat

Now my system is nopt C:, but F: i used cmd to open a console windows typed it in cd kderootemerge then next line is
F:kderootemerge>

I put in kdeenv.bat and come up with the system can not find the path specified. < was unexpected this time.

Dunno what i am doing wrong here! The file is there plain as day?

Thinking maybe it has to do with Configure the emerge tool section above the emerge section i was talking about.

Copy the file %KDEROOT%emergekdesettings-example.bat as %KDEROOT%etckdesettings.bat and change its contents according to your needs. The options are described in the rem lines in the file itself.

Ok i tryed opening this i installed a fresh copy of windows on my harddrisk using windows xp pro! I've download the compilers sdks of sorts and sql and python been following this tut by the book. I notice when editing this file as said in tut they are reffering to %KDEROOT% , but we made our own directory mine is k:/kderoot. Sinc ein linux they change my other drive to letter c it was used so using k and it can't be changed with out a reinstall and i just downloaded all this software ack!

Anyway back to setting this file up to my needs also noticed
%PROGRAMFILES%, and other %KDEROOT% and %PATH% and such think i only changed 1 and it was the kde directory set to f:kderoot cause wasn't asking for a path. The other ones i pointed to the directories to where they are to be set but left the %PROGRAMFILES% even though mine is Program Files in my tree. I left for the reason of at the end of the file says do't edit so i am asumeing that these are used to be call am i not.

I did noticed though when dowloading emerge not to use the ref name %KDEROOT% but the name i chosen f:kderoot hence how i got emerge on my computer.

So i don't know what i am really doing wrong. I tryed and set a few of the .bat to echo on and after wards sometimes one of them disappear so i have to redownload the emerge. It doesn't come out like the tut so where am i going wrong i keep asking my self. Need Help here!!

Last edited by CourtJesterG on Mon Dec 01, 2008 6:44 pm, edited 1 time in total.
Vx++
Registered Member
Posts
9
Karma
0
I think your fault is in the kdesettings.bat, maybe you can post it's content here an we can help you...

Greetings


Vx++, proud to be a member of KDE forums since 2008-Oct.
User avatar
CourtJesterG
Registered Member
Posts
3
Karma
0

RE: Developeing with KDE4 on windows

Tue Dec 02, 2008 10:58 am
@echo off
rem Here you set the base directory under which the whole KDE
rem subsystem will live.
set KDEROOT=F:kderoot

rem Here you set the compiler to be used.
rem * mingw - use the mingw gcc compiler (recommended)
rem * msvc2005 - use the Microsoft Visual C++ 2005 compiler
rem * msvc2008 - use the Microsoft Visual C++ 2008 compiler
set KDECOMPILER=msvc2008

rem Here you set the path to your Python installation,
rem so that Python will be found, when Python scripts are be executed.
rem By setting this here, you don't have to change the global environment
rem settings of Windows.
set PYTHONPATH=%PROGRAMFILES%python25

rem Here you set the path to msys if you want to compile
rem automake-based projects (only needed for some internal packages).
set MSYSDIR=%KDEROOT%msys

rem Here you set the path to your platform SDK installation.
rem This path will be automatically included then.
set PSDKDIR=%PROGRAMFILES%Microsoft SDKs
rem Here you set the path to your Microsoft DirectX SDK installation
rem This is not needed if you use MinGW
set MSDXSDKDIR=%PROGRAMFILES%Microsoft DirectX SDK (November 2008)

rem Here you set the location of the vcvarsall.bat file that adds
rem Visual C++ environment variables into the build environment.
rem if you are not building on x86 change that to something appropriate.

if %KDECOMPILER% == msvc2005 call "%MSDXSDKDIR%Utilitiesbindx_setenv.cmd" && call "%PROGRAMFILES%Microsoft Visual Studio 8VCvcvarsall.bat" x86

if %KDECOMPILER% == msvc2008 call "%MSDXSDKDIR%Utilitiesbindx_setenv.cmd" && call "%PROGRAMFILES%Microsoft Visual Studio 9.0VCvcvarsall.bat" x86

rem Here you change the download directory.
rem If you want, so you can share the same download directory between
rem mingw and msvc.
set DOWNLOADDIR=%KDEROOT%download

rem Here you can tell the emerge tool in which dir you want to save the
rem SVN checkout of KDE source code. If you have SVN account registered
rem within the KDE project, you can also set KDESVNUSERNAME and change
rem KDESVNSERVER from svn://anonsvn.kde.org to https://svn.kde.org or
rem svn+ssh://username@svn.kde.org, so that rem you can directly commit
rem your changes from the emerge's SVN checkout. In case you use svn+ssh,
rem also run plink username@svn.kde.org after executing kdeenv.bat or
rem svn will hang forever
set KDESVNDIR=%KDEROOT%svn
set KDESVNSERVER=svn://anonsvn.kde.org
set KDESVNUSERNAME=username

rem Here you can tell the emerge tool password for the SVN access
rem if you have SVN account registered within the KDE project.
rem For security reasons you should better log in to the KDE server by hand
rem using the command line Subversion 'svn' command: enter the username
rem and password at the first login, e.g. when you checkout the emerge
rem directory. The Subversion client will then remember the password so it
rem does not have to be written down here.
rem set KDESVNPASSWORD=

rem If you use svn+ssh, you will need a ssh-agent equaivalent for managing
rem the authorization. Pageant is provided by the Putty project, get it at
rem http://www.chiark.greenend.org.uk/~sgta ... nload.html
rem and make sure that plink is in your PATH and Pageant is configured
rem (you need to import your key)
set SVN_SSH=plink

rem If you want to use emerge.py together with the kdewin-installer,
rem you should set the value of directory_layout to 'installer'.
rem If you leave it unset or set it to 'traditional' you get the category
rem sublayout.
rem Note: it is not recommended anymore to use the traditional layout.
set directory_layout=installer

rem Here you can set type of the emerge build.
rem There are two standard build types: Debug and Release.
rem Both are used if no EMERGE_BUILDTYPE is set.
rem There is a third extra buildtype called RelWithDebInfo, which is
rem release (optimized) build but containing debugging information.
rem You can override the build type at the commandline using
rem the '--buildtype=[BuildType]' option. The build type which is set here
rem will not override the buildtype in .py package files.
set EMERGE_BUILDTYPE=RelWithDebInfo

rem If you want to have verbose output, uncomment the following option
rem and set it to positive integer for verbose output and to 0
rem or disable it for normal output. Currently the highest verbosity level
rem is 3 (equal to 'emerge -v -v -v'). level 0 equals 'emerge -q'
set EMERGE_VERBOSE=1

rem Enable this option if you want to have shorter build times, and less
rem disk usage. It will then avoid copying source code files of the KDE
rem svn repository. The disadvantage is that you cannot make packages when
rem this option is set. To disable, set EMERGE_NOCOPY=False.
set EMERGE_NOCOPY=True

rem If you want to build all packages with buildTests option, enable
rem this option. Applies only to the cmake based packages.
rem set EMERGE_BUILDTESTS=True

rem This option only applies if you want to make packages. It sets
rem the output directory where your generated packages should be stored.
rem set EMERGE_PKGDSTDIR=%KDEROOT%tmp

rem No editing should be necessary below this line (in an ideal world)
rem ##################################################################

set PATH=%PYTHONPATH%;%PATH%

echo kdesettings.bat executed
echo KDEROOT : %KDEROOT%
echo KDECOMPILER : %KDECOMPILER%
echo KDESVNDIR : %KDESVNDIR%
echo PYTHONPATH : %PYTHONPATH%
echo DOWNLOADDIR : %DOWNLOADDIR%



---------------------------------------------------
Note even in cmd when i get to the point to execute the file even if i put just the file name doesn't go through nor does using the START command [Filename] FILE DOESN'T EXIST. been reading alot of the help in cmd and svn noticed there isn't alot of input on there commands. Also when i do load cmd the drive and path starts as this and what i've been typeing.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

F:Documents and SettingsCourtJesterG>cdkderootemerge

F:kderootemerge>kdeenv.bat

F:kderootemerge>
----------------------------------------------------------------Also if i put
cd kderootemerge it shows as the same input as above i don't get the output at all that is showen in tut. If i type emerge --help it doesn't go through

I do have MiniGW install along with MSV2008 Express version i dowload with is bundled with the microsoft sql server, got the drx sdk and a folder microsoft SDKs i asume is the server platform directoies all these went default to my /Programs Files/ dIRECTORY.

Yeah any help would be great.

Also just noticed after i ran that i clicked on the kdeenv.bat went to edit to share it as well it is empty now nothing is in it. Maybe it worked or bugged? Not used to cmd. I got a c++ book with me and applyed for college in computer science messed with it when i was younger so its been years. I really like KDE and linux actually but switched back to Windows cause the directx i like my pc game i paid for to be able to play it since wine couldn't get it running. I have two harddrives an 80GB and a 20GB installed nothing is on my 20GB but not used to raid and i believe raid 0 you need to have the same harddrives. I really wanted to duel boot but as you see its an 80gb harddrive and the 20gb.

Also notice they do have a newer version of Python out 2.6 but this is not compatible with the new svu program so running 2.5.

Spring college for computer science

Thanks ;)

Last edited by CourtJesterG on Tue Dec 02, 2008 11:22 am, edited 1 time in total.
Vx++
Registered Member
Posts
9
Karma
0
I see several lines in your kdesettings.bat which look like that:

Code: Select all
PYTHONPATH=%PROGRAMFILES%python25


Try to change them to the real path, like
Code: Select all
PYTHONPATH=c:ProgrammFilespython25

that.

At the moment I'm not at home, so I can't post you my version! But I'll do that later.

Greetings


Vx++, proud to be a member of KDE forums since 2008-Oct.
Vx++
Registered Member
Posts
9
Karma
0
So, finally...mine looks like that:

Code: Select all
@echo off
rem Here you set the base directory under which the whole KDE
rem subsystem will live.
set KDEROOT=F:KDE

rem Here you set the compiler to be used.
rem * mingw - use the mingw gcc compiler (recommended)
rem * msvc2005 - use the Microsoft Visual C++ 2005 compiler
rem * msvc2008 - use the Microsoft Visual C++ 2008 compiler
set KDECOMPILER=msvc2005

rem Here you set the path to your Python installation,
rem so that Python will be found, when Python scripts are be executed.
rem By setting this here, you don't have to change the global environment
rem settings of Windows.
set PYTHONPATH=F:python26

rem Here you set the path to msys if you want to compile
rem automake-based projects (only needed for some internal packages).
set MSYSDIR=F:KDEmsys

rem Here you set the path to your platform SDK installation.
rem This path will be automatically included then.
set PSDKDIR=C:ProgrammeMicrosoft Platform SDK for Windows Server 2003 R2
rem Here you set the path to your Microsoft DirectX SDK installation
rem This is not needed if you use MinGW
set MSDXSDKDIR=C:ProgrammeMicrosoft DirectX SDK (August 2008)

rem Here you set the location of the vcvarsall.bat file that adds
rem Visual C++ environment variables into the build environment.
rem if you are not building on x86 change that to something appropriate.

if %KDECOMPILER% == msvc2005 call "%MSDXSDKDIR%Utilitiesbindx_setenv.cmd" && call "C:ProgrammeMicrosoft Visual Studio 8VCvcvarsall.bat" x86

if %KDECOMPILER% == msvc2008 call "%MSDXSDKDIR%Utilitiesbindx_setenv.cmd" && call "C:ProgrammeMicrosoft Visual Studio 9.0VCvcvarsall.bat" x86

rem Here you change the download directory.
rem If you want, so you can share the same download directory between
rem mingw and msvc.
set DOWNLOADDIR=F:KDEdownload

rem Here you can tell the emerge tool in which dir you want to save the
rem SVN checkout of KDE source code. If you have SVN account registered
rem within the KDE project, you can also set KDESVNUSERNAME and change
rem KDESVNSERVER from svn://anonsvn.kde.org to https://svn.kde.org or
rem svn+ssh://username@svn.kde.org, so that rem you can directly commit
rem your changes from the emerge's SVN checkout. In case you use svn+ssh,
rem also run plink username@svn.kde.org after executing kdeenv.bat or
rem svn will hang forever
set KDESVNDIR=%KDEROOT%svn
set KDESVNSERVER=svn://anonsvn.kde.org
set KDESVNUSERNAME=username

rem Here you can tell the emerge tool password for the SVN access
rem if you have SVN account registered within the KDE project.
rem For security reasons you should better log in to the KDE server by hand
rem using the command line Subversion 'svn' command: enter the username
rem and password at the first login, e.g. when you checkout the emerge
rem directory. The Subversion client will then remember the password so it
rem does not have to be written down here.
rem set KDESVNPASSWORD=password

rem If you use svn+ssh, you will need a ssh-agent equaivalent for managing
rem the authorization. Pageant is provided by the Putty project, get it at
rem http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
rem and make sure that plink is in your PATH and Pageant is configured
rem (you need to import your key)
set SVN_SSH=plink

rem If you want to use emerge.py together with the kdewin-installer,
rem you should set the value of directory_layout to 'installer'.
rem If you leave it unset or set it to 'traditional' you get the category
rem sublayout.
rem Note: it is not recommended anymore to use the traditional layout.
set directory_layout=installer

rem Here you can set type of the emerge build.
rem There are two standard build types: Debug and Release.
rem Both are used if no EMERGE_BUILDTYPE is set.
rem There is a third extra buildtype called RelWithDebInfo, which is
rem release (optimized) build but containing debugging information.
rem You can override the build type at the commandline using
rem the '--buildtype=[BuildType]' option. The build type which is set here
rem will not override the buildtype in .py package files.
set EMERGE_BUILDTYPE=RelWithDebInfo

rem If you want to have verbose output, uncomment the following option
rem and set it to positive integer for verbose output and to 0
rem or disable it for normal output. Currently the highest verbosity level
rem is 3 (equal to 'emerge -v -v -v'). level 0 equals 'emerge -q'
set EMERGE_VERBOSE=1

rem Enable this option if you want to have shorter build times, and less
rem disk usage. It will then avoid copying source code files of the KDE
rem svn repository. The disadvantage is that you cannot make packages when
rem this option is set. To disable, set EMERGE_NOCOPY=False.
set EMERGE_NOCOPY=True

rem If you want to build all packages with buildTests option, enable
rem this option. Applies only to the cmake based packages.
rem set EMERGE_BUILDTESTS=True

rem This option only applies if you want to make packages. It sets
rem the output directory where your generated packages should be stored.
rem set EMERGE_PKGDSTDIR=%KDEROOT%tmp

rem No editing should be necessary below this line (in an ideal world)
rem ##################################################################

set PATH=%PYTHONPATH%;%PATH%

echo kdesettings.bat executed
echo KDEROOT     : %KDEROOT%
echo KDECOMPILER : %KDECOMPILER%
echo KDESVNDIR   : %KDESVNDIR%
echo PYTHONPATH  : %PYTHONPATH%
echo DOWNLOADDIR : %DOWNLOADDIR%


Hope this helps you a little bit ;)


Greetings


Vx++, proud to be a member of KDE forums since 2008-Oct.
User avatar
CourtJesterG
Registered Member
Posts
3
Karma
0
Thanks i will try that! See in the tut it says refer too with the %KDEROOT% i wonder also if i really am suppose to use that all through. I also did think maybe in that file all the paths to change.

I was running IE with no firewall or nothing. Guess what happened freaken thing downloaded some stuff went to remove it my computer went zombie on me couldn't do nothing even after restart and everything just sit idle running in windows. If checked processes grrr. Trogan virus city. I reinstalled a fresh version of win xp pro. Running seamonkey i am surprised that the firefox in linux is seamonkey just a different paint job i believe. Also the more i look at xp and everything the more i see the KDE isn't that strange! Only thing missing is the my plasma folder/desktop on my background, a nice doliphn to play with and kate. Oh the nice file system too. Noticed in actually its built almost the same way even does have a so called root, but they prompt you to make a password when installing. You can run as a power user from computer management. As for updates i only installed the netframes and windows advantage those are the only updates i installed from microsoft. Only ones i need forget the rest of the stuff.

Need to make a backup disk tired of reinstalling this mojojo. Then going to proceded to install the stuff that was in here and try this all again.


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]