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

help building for windows

Page 1 of 1 (3 posts)

Tags: None
(comma "," separated)
mattmaddex
Registered Member
Posts
2
Karma
0

help building for windows

Sat Apr 06, 2013 6:17 pm
Hello all - I'm attempting to follow these instructions on building Calligra for windows. This is my first attempt building something in windows so if it seems I'm not understanding a concept I will take no offense at dumbed down explanations.

I have three two (Number 1 seems obvious to me now) questions at this point:
  1. The instruction say to
    Be sure to switch to the kde-4.8 branch.
    Am I correct in assuming this is what's being accomplished with this command
    Code: Select all
    git checkout kde-4.8
  2. When I edit the 'etc/kdesettings.bat' file I do not see the WINDOWSSDKDIR variable to update per this instruction
    Update WINDOWSSDKDIR to point to your installation of the Windows SDK
    I included kdesettings.bat file at the bottom of this post, I took a guess and updated PSDKDIR since I didn't see WINDOWSSDKDIR
    Code: Select all
    set PSDKDIR=C:\Windows\Microsoft.NET\Framework\v4.0.30319
    Is this correct or should I add a line of code to create a WINDOWSSDKDIR variable?

  3. When I navigate to the emerge directory and call kdeenv i get the following (FYI I'm running this from Git Bash not windows cmd linerunning from windows command line):
    Code: Select all
    C:\kderoot\emerge>kdeenv.bat
    kdesettings.bat executed
    Invalid parameter - C:\kderoot
    Invalid parameter - C:\kderoot
    Invalid parameter - C:\kderoot\download
    Invalid parameter - C:\kderoot\download
    Invalid parameter - C:\kderoot\svn
    Invalid parameter - C:\kderoot\svn
    Invalid parameter - C:\kderoot\git
    Invalid parameter - C:\kderoot\git
    'C:\kderoot' is not recognized as an internal or external command,
    operable program or batch file.
    KDEROOT     : C:\kderoot\
    KDECOMPILER : msvc2010
    KDESVNDIR   : C:\kderoot\svn\
    KDEGITDIR   : C:\kderoot\git\
    PYTHONPATH  : C:\Python32
    DOWNLOADDIR : C:\kderoot\download\
    The system cannot find the path specified.
    Using Platform SDK: C:\Windows\Microsoft.NET\Framework\v4.0.30319

    C:\kderoot>

    4. kdesettings.bat:
Code: Select all
@echo off

rem Here you set the base directory under which the whole KDE subsystem will

live.
set KDEROOT=C:\kderoot

rem ####### Compiler settings #######

rem Here you set the compiler to be used.
rem * mingw4   - use the mingw gcc compiler (recommended)
rem * mingw    - use the mingw gcc compiler (gcc Version 3.4.5 -
rem               please only use this option if you are exactly
rem               sure about the consequences)
rem * msvc2008 - use the Microsoft Visual C++ 2008 compiler
rem * msvc2010 - use the Microsoft Visual C++ 2010 compiler
rem * msvc2012 - use the Microsoft Visual C++ 2012 compiler
set KDECOMPILER=msvc2010

rem Here you can set the architecure for which packages are build.
rem Currently x86 (32bit), x64 (64) and arm (wince) are supported
rem
rem               x86  x64  arm-wince
rem  mingw4        x    x       x[1]
rem  mingw         x   ---     ---
rem  msvc2005      x   ---     --- 
rem  msvc2008      x   ---     ---
rem  msvc2010      x   ---     ---
rem
rem [1] by dev-utils/cegcc-arm-wince package
rem
set EMERGE_ARCHITECTURE=x86
rem set EMERGE_ARCHITECTURE=x64

rem ####### Directory settings #######

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 This option defines the location for git checkouts.
set KDEGITDIR=%KDEROOT%\git
rem This option defines the location for svn checkouts.
set KDESVNDIR=%KDEROOT%\svn

rem substitute pathes by drives
rem This option is needed to avoid path limit problems in case of long base

pathes
rem and compiling big packages like qt
rem If you disable it do _not_ use any paths longer than 6 letters in the
rem directory settings
set EMERGE_USE_SHORT_PATH=1

rem each drive could be commented out to skip substution
rem set EMERGE_ROOT_DRIVE=r:
rem set EMERGE_SVN_DRIVE=s:
rem set EMERGE_GIT_DRIVE=q:
rem set EMERGE_DOWNLOAD_DRIVE=t:

rem ####### SVN Settings #######

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 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 once
rem to accept the fingerprint of the server or svn will hang forever when
rem trying to download from the server.

set KDESVNSERVER=svn://anonsvn.kde.org
set KDESVNUSERNAME=username

rem If you do not mind getting the output of the svn commands, then enable this
rem option
rem set KDESVNVERBOSE=True

rem Non kde svn repository checkouts will be placed below %DOWNLOADDIR%/svn-

src/<package>
rem By default the emerge svn module supports only single branch svn checkouts.
rem With this option emerge assumes that the svn repository have the svn standard

layout
rem and will create related subdirectories for trunk, branches and tags below the

above
rem mentioned root directory.
rem set EMERGE_SVN_STDLAYOUT=1

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 ####### Git Settings #######

rem With this option set emerge checks out each git repository branch into a
rem separate subdirectory (see git clone --mirror at git clone  --shared --

local).
rem Without this option changing the branch will overwrite previous checkouts.
rem Note: Changing the value invalidates available checkouts of related packages
rem and requires a remove of the complete source dir.
rem set EMERGE_GIT_MULTIBRANCH=True

rem Setting up variables for git, not needed by emerge but preventing trouble
rem with corrupted git pushes
set GIT_SSH=plink
set HOME=%USERPROFILE%
rem set GIT_AUTHOR_NAME=authorname
rem set GIT_AUTHOR_EMAIL=email
rem set GIT_COMMITTER_NAME=username
rem set GIT_COMMITTER_EMAIL=email

rem ####### Python Settings #######

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. In case python is distributed with emerge the
rem following setting is not used.
if "%PYTHONPATH%" == "" (
    set PYTHONPATH=C:\Python32
)

rem ####### Proxy Settings #######

rem proxy settings - in case a proxy is required uncomment the following

variables
rem set EMERGE_PROXY_HOST=
rem set EMERGE_PROXY_PORT=8080
rem set EMERGE_PROXY_USERNAME=
rem set EMERGE_PROXY_PASSWORD=

rem Here you can set if emerge should not try to download files in passive mode
rem set EMERGE_NO_PASSIVE_FTP=True

rem ####### Visual Studio Settings #######

rem Here you can adjust the path to your Visual Studio installation if needed
rem This is used to set up the build environment automatically
if %KDECOMPILER% == msvc2008 set VSDIR=%PROGRAM_FILES%\Microsoft Visual Studio

9.0
if %KDECOMPILER% == msvc2010 set VSDIR=%PROGRAM_FILES%\Microsoft Visual Studio

10.0
if %KDECOMPILER% == msvc2012 set VSDIR=%PROGRAM_FILES%\Microsoft Visual Studio

11.0

rem Here you can adjust the path to the Windows Mobile SDK installation
rem This is used to set up the cross-compilation environment automatically
if "%EMERGE_TARGET_PLATFORM%" == "WM50" set TARGET_SDKDIR=%PROGRAM_FILES%\Windows

Mobile 5.0 SDK R2\PocketPC
if "%EMERGE_TARGET_PLATFORM%" == "WM60" set TARGET_SDKDIR=%PROGRAM_FILES%\Windows

Mobile 6 Professional SDK\PocketPC
if "%EMERGE_TARGET_PLATFORM%" == "WM65" set TARGET_SDKDIR=%PROGRAM_FILES%\Windows

Mobile 6 Professional SDK\PocketPC

rem Here you can set a specific platform SDK to use with the Visual Studio

toolchain
rem Normally this is not needed as a default platform SDK is set by the build

environment script
rem set PSDKDIR=%PROGRAM_FILES%\Microsoft SDKs\Windows\v6.0A
set PSDKDIR=C:\Windows\Microsoft.NET\Framework\v4.0.30319
rem set WINDOWSSDKDIR=C:\Windows\Microsoft.NET\Framework\v4.0.30319

rem Here you can set the path to your Microsoft DirectX SDK installation
rem This is not needed if you use MinGW or won't use the directx backend for

Phonon
rem set MSDXSDKDIR=%PROGRAM_FILES%\Microsoft DirectX SDK (August 2009)

rem ####### Build Type Settings #######

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.
if "%1" == "debug" (
set EMERGE_BUILDTYPE=Debug
)
if "%1" == "relwithdebinfo" (
set EMERGE_BUILDTYPE=RelWithDebInfo
)
if "%1" == "release" (
set EMERGE_BUILDTYPE=Release
)
if "%1" == "" (
set EMERGE_BUILDTYPE=RelWithDebInfo
)

rem ####### Various Emerge Settings #######

rem This option can be used to build only source packages and don't use binary

packages
rem it is needed for wince builds, but works everywhere and is the recommended

way to
rem use emerge.
set EMERGE_SOURCEONLY=True

rem override specific emerge options
rem This option makes it possible to set properties, which are defined in
rem bin\options.py. Multiple entries are separated by a space
rem Please note that properties may be overriden by dedicated package
rem  Example:
rem    * set EMERGE_OPTIONS=cmake.useIDE=1 install.useMakeToolForInstall=1
rem set EMERGE_OPTIONS=

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. To disable, set EMERGE_NOCOPY=False.
set EMERGE_NOCOPY=True

rem By default emerge will merge all package into KDEROOT. By setting the

following
rem option to true, the package will be installed into a subdir of KDEROOT.
rem The directory is named like the lower cased build type
rem When using this option you can run emerge/kdeenv.bat with the build mode type
rem parameter (release, releasedebug or debug) to have different shells for each
rem build type.
rem set EMERGE_MERGE_ROOT_WITH_BUILD_TYPE=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 This option can be used to override the default make program
rem change the value to the path of the executable you want to use instead.
set EMERGE_MAKE_PROGRAM=%KDEROOT%\dev-utils\bin\jom.exe

rem This option can be used to set the default category for packages with the

same name
rem that are contained in multiple categories; This is especially useful if you

want
rem to build e.g. from the 4.3 branch: simply set the variable to kde-4.3 then
rem for all other packages this option doesn't have any effect
rem set EMERGE_DEFAULTCATEGORY=kde-4.3

rem This option can be used to set a directory where build logs are saved
rem instead of being printed to the console. Logging information is appended to
rem existing logs.
rem set EMERGE_LOG_DIR=%KDEROOT%\buildlogs

rem This option can be used to integrate packages from other portage directories
rem or override the default packages. The default directory can be overridden by
rem not including it in this list. If you do not set this option emerge will take
rem the current portage directory instead.
rem set EMERGE_PORTAGE_ROOT=C:\test\portage;%KDEROOT%\emerge\portage

rem This option enables separating of package build dependencies from emerge

internal
rem dependencies. When enabled packages depends on packages from the internal

category
rem too. The packages from the internal package belongs to the related python

class
rem with the same name. They provide a standardized way to define runtime

dependencies
rem for emerge itself.
rem note: After finishing the testing phase this feature will be enabled by

default
rem and this option removed.
rem set EMERGE_ENABLE_IMPLICID_BUILDTIME_DEPENDENCIES=1

rem The following option makes the emerge run fail if applying patches fails
rem the default is that failing patches do not result in a stop
rem set EMERGE_HOLD_ON_PATCH_FAIL=True

rem emerge supports two type of package state and manifest databases: a file

based and
rem an sqlite based. The file based database interacts better with kdewin
rem installer/packager eg. you can directly integrate binary packages while the
rem sqlite based database seems to be slighty faster but is only accessable
rem through the emerge command line. This option let you choose the used on.
rem By default the sqlite database is not used, because the implementation
rem results into errors on qmerge action.
rem set EMERGE_ENABLE_SQLITEDB=FALSE

rem ####### Cross Compiling

rem The following variables are used for cross-compiling to Windows Mobile /

WinCE
rem when uncommented, the proper toolchain is set up for the specified target OS

and architecture.
rem EMERGE_TARGET_PLATFORM currently supports :
rem * WM50 - Windows Mobile 5.0 PocketPC (based on WinCE 5.01)
rem * WM60 - Windows Mobile 6.0 Professional (based on WinCE 5.02)
rem * WM65 - Windows Mobile 6.5 Professional (based on WinCE 5.02)
rem EMERGE_TARGET_ARCHITECTURE currently supports :
rem * ARMV4I (all platforms)
rem set EMERGE_TARGET_PLATFORM=WM60
rem set EMERGE_TARGET_ARCHITECTURE=ARMV4I

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

rem internal used settings version only for emerge maintainers
rem increment for each definition change in this file and fix version
rem issues in kdeenv.bat
rem Note: unset EMERGE_SETTINGS_VERSION means version 0
SET EMERGE_SETTINGS_VERSION=1

echo kdesettings.bat executed

Last edited by mattmaddex on Mon Apr 08, 2013 5:07 pm, edited 1 time in total.
User avatar
scummos
Global Moderator
Posts
1175
Karma
7
OS

Re: help building for windows

Mon Apr 08, 2013 10:19 am
I have no idea about building on windows, but to me it looks like you need to run that script from the windows shell instead of the git one, no? Did you try that?

Cheers,
Sven

I'm working on the KDevelop IDE.
mattmaddex
Registered Member
Posts
2
Karma
0

Re: help building for windows

Mon Apr 08, 2013 5:09 pm
Yeah I should have been doing that in the windows command line. I've edited the initial post to reflect what's going on now.

Thanks,

Matt.

Page 1 of 1 (3 posts)

Bookmarks


Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell