#135 MinGW and Visual C++ 2005 Support

0.61
closed
None
5
2014-08-24
2006-06-16
Peter Kuemmel
No

Attached files for building on Windows, tested with
msvc and mingw.

- unpack the files into aspen/win32
- apply win32-build.patch
- start cygwin/msys autogen to generate files,
don't build

Building with the cmake build system:

install CMake 2.4.2 or CVS version from www.cmake.org

Building Visual C++ 2005 project files:
- install Visual C++ 2005
- create a build directory, e.g. .../trunk/../build
- call in the build directory 'cmake
..\trunk\development\cmake'
- start lyx.sln

Building with GCC/Windows:
- create a build directory, e.g. .../trunk/../build
- call in the build directory 'cmake
..\trunk\development\cmake'

To generate other build files call 'cmake'
which shows a list of possibilities:

The following generators are available on this platform:
Borland Makefiles = Generates Borland
makefiles.
MSYS Makefiles = Generates MSYS makefiles.
MinGW Makefiles = Generates a make file
for use with
mingw32-make.
NMake Makefiles = Generates NMake makefiles.
Unix Makefiles = Generates standard UNIX
makefiles.
Visual Studio 6 = Generates Visual Studio
6 project files.
Visual Studio 7 = Generates Visual Studio
.NET 2002 project
files.
Visual Studio 7 .NET 2003 = Generates Visual Studio
.NET 2003 project
files.
Visual Studio 8 2005 = Generates Visual Studio
.NET 2005 project
files.
Visual Studio 8 2005 Win64 = Generates Visual Studio
.NET 2005 Win64
project files.
Watcom WMake = Generates Watcom WMake
makefiles.

Discussion

  • Peter Kuemmel
    Peter Kuemmel
    2006-08-31

    Logged In: YES
    user_id=1159765

    UPADTE:

    - unpack win32-aug-06.zip into aspell/win32

    - in aspell/ call
    "patch -p0 -i win32/win32_build.patch"

    - in your_build_directory/ call
    "cmake ..\aspell\win32"

    The patch supports the
    registry under Windodws.

    WIN32PORT functions are
    used for the Windows file
    handling.

     
  • Peter Kuemmel
    Peter Kuemmel
    2006-08-31

    Logged In: YES
    user_id=1159765

    Readme.txt:

    You need cmake and cygwin.

    - unpack win32-aug-06.zip into aspell/win32

    - with cygwin patch aspell: in aspell/ call
    "patch -p0 -i win32/win32-build.patch"

    - generate missing source files with cygwin:
    ./autogen

    - build msvc files in a cmd.exe shell:
    in your_build_directory call
    "cmake ..\aspell\win32"

    - build mingw files in a cmd.exe shell:
    in your_build_directory call
    "cmake -G"MinGW Makefiles" ..\aspell\win32"

     
  • Peter Kuemmel
    Peter Kuemmel
    2006-09-07

     
    Attachments
  • Kevin Atkinson
    Kevin Atkinson
    2006-11-13

    • milestone: --> 660004
     
  • Kevin Atkinson
    Kevin Atkinson
    2006-11-13

    • assigned_to: nobody --> kevina
     
  • Kevin Atkinson
    Kevin Atkinson
    2006-11-18

    Logged In: YES
    user_id=6591
    Originator: NO

    I take it your patch is meant for CVS HEAD and not Aspell 0.60.4?

     
  • Kevin Atkinson
    Kevin Atkinson
    2006-11-18

    • milestone: 660004 --> 0.61
     
  • Peter Kuemmel
    Peter Kuemmel
    2006-11-18

    Logged In: YES
    user_id=1159765
    Originator: YES

    Yes against head.

     
  • Logged In: YES
    user_id=798735
    Originator: NO

    Any news on this? I could compile aspell 0.60.5 with an own set of cmakefiles with mingw. also creating german dictionary worked fine...

     
  • Kevin Atkinson
    Kevin Atkinson
    2008-05-13

    Logged In: YES
    user_id=6591
    Originator: NO

    So are these changes still relevant or have they been succeeded by Patch 1751606 (http://sourceforge.net/tracker/index.php?func=detail&aid=1751606&group_id=245&atid=300245)

     
  • Logged In: YES
    user_id=798735
    Originator: NO

    The patches for the sources are fine but providing hand-crafted project-files is just stupid.
    a) as soon as something in the code layout changes you have to fix all of them (the same way)
    b) what if I want to have msvc2003 or msvc2008 solutions?
    c) or simple nmake Makefiles?

    in contrast to a CMake script
    - it can be used on every platform where cmake is available (windows, linux, mac, aix, ...)
    - it can create a lot of different makefile types and project solutions
    - it's much easier to maintain than msvc solutions
    - we (kde-windows) can't use msvc solutions for our automated buildsystem

    So my advise - don't check in the solutions but switch to cmake like many other projects did (or doing atm)

     
  • Logged In: YES
    user_id=798735
    Originator: NO

    No comment? :(

    Would you mind taking a look at a new CMake script which compiles 0.60.6 out of the box on linux? It would be a really great improvement when kde-windows could compile aspell with cmake instead using pre-compiled binaries from somehwere.

     
  • Peter Kuemmel
    Peter Kuemmel
    2008-05-25

    Logged In: YES
    user_id=1159765
    Originator: YES

    The cmake files could be maintained in one additional folder and will not pollute the repository. That's we way we've done it in D-Bus:

    http://gitweb.freedesktop.org/?p=dbus/dbus.git;a=tree

     
  • Kevin Atkinson
    Kevin Atkinson
    2008-05-25

    Logged In: YES
    user_id=6591
    Originator: NO

    I am highly unlikely to switch to a completely different build system until at least Aspell 0.61 and even than it will take a lot of through and a decent deal of work to completely switch over.

    The CMake script included in the zip file looks way to basic for it to be suitable to replace the current build system.

    I might consider including it as I means to compile for Windows.

     
  • Kevin Atkinson
    Kevin Atkinson
    2008-05-25

    Logged In: YES
    user_id=6591
    Originator: NO

    Sorry s/through/thought/.

     
  • Logged In: YES
    user_id=798735
    Originator: NO

    We don't want to replace it at all (at least not in the first step). We want to have a buildsystem that works on windows at all. The current solution is not usable.
    And I also said I'm going to write a better script if you're interested in with a lot of checks for specific things. In fact I already wrote one but it currently only works on linux because of win32 compile problems and assumptions due to the hard-coded .vcproj crap. But before I post it here I wanted to be sure if you're interested.

     
  • Kevin Atkinson
    Kevin Atkinson
    2008-05-25

    Logged In: YES
    user_id=6591
    Originator: NO

    chehrlic:

    Yes I am interested if it is an alternative build system and does not get it the way of the standard build.

    However, I can not promise to maintain it or keep it up to date. Before a release I will at least try to use cmake to build an Aspell binary on my Linux system, but if that fails and it is not an easy fix I will likely just leave it broken.

    Please submit as a separate patch.

     
  • Peter Kuemmel
    Peter Kuemmel
    2008-05-25

    Logged In: YES
    user_id=1159765
    Originator: YES

    As Christian said, we don't wanna replace it.
    As in dbus it should be an alternative.
    dbus would never switch from is auto build system.

    Best would be, if you give Christian write access to the repro.
    Then, I'm sure, Christian would promise to not touch other files
    than the cmake files without a OK from you.

    We even do not await that you maintain the cmake build system.
    We just wanna have your OK to work on the cmake files.

     
  • Peter Kuemmel
    Peter Kuemmel
    2008-05-25

    Logged In: YES
    user_id=1159765
    Originator: YES

    Without good cross-platform support aspell will die
    because other software depends on spell-checking on
    at least Linux, Mac OS, and Windows.

     
  • Kevin Atkinson
    Kevin Atkinson
    2008-05-27

    Logged In: YES
    user_id=6591
    Originator: NO

    The CMake patch has been submitted separately (1971805) so I am closing this patch.

     
  • Kevin Atkinson
    Kevin Atkinson
    2008-05-27

    • status: open --> closed