Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build Python with VS 2005(MSVC8) #45789

Closed
weck mannequin opened this issue Nov 15, 2007 · 3 comments
Closed

Build Python with VS 2005(MSVC8) #45789

weck mannequin opened this issue Nov 15, 2007 · 3 comments
Labels
build The build process and cross-build topic-installation

Comments

@weck
Copy link
Mannequin

weck mannequin commented Nov 15, 2007

BPO 1448
Nosy @loewis, @tiran
Files
  • pcbuild8.patch
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2007-11-15.18:32:15.781>
    created_at = <Date 2007-11-15.15:08:14.390>
    labels = ['build', 'expert-installation']
    title = 'Build Python with VS 2005(MSVC8)'
    updated_at = <Date 2007-11-15.18:32:15.780>
    user = 'https://bugs.python.org/weck'

    bugs.python.org fields:

    activity = <Date 2007-11-15.18:32:15.780>
    actor = 'loewis'
    assignee = 'none'
    closed = True
    closed_date = <Date 2007-11-15.18:32:15.781>
    closer = 'loewis'
    components = ['Installation']
    creation = <Date 2007-11-15.15:08:14.390>
    creator = 'weck'
    dependencies = []
    files = ['8753']
    hgrepos = []
    issue_num = 1448
    keywords = ['patch']
    message_count = 3.0
    messages = ['57531', '57538', '57544']
    nosy_count = 3.0
    nosy_names = ['loewis', 'christian.heimes', 'weck']
    pr_nums = []
    priority = 'normal'
    resolution = 'rejected'
    stage = None
    status = 'closed'
    superseder = None
    type = 'compile error'
    url = 'https://bugs.python.org/issue1448'
    versions = ['Python 2.6', 'Python 3.0']

    @weck
    Copy link
    Mannequin Author

    weck mannequin commented Nov 15, 2007

    There are several problems that cause us can't build python with vs
    2005.

    1. some libraries are outdated.

    for example, tcl8.4.12, tk8.4.12. Just download a newer version will
    resolve this problem.
    wget http://prdownloads.sourceforge.net/tcl/tcl8.4.16-src.tar.gz
    wget http://prdownloads.sourceforge.net/tcl/tk8.4.16-src.tar.gz
    wget http://prdownloads.sourceforge.net/tix/Tix8.4.2-src.tar.gz

    I think it's better to upgrade bdb too, so i select bdb 4.6.21.
    http://download.oracle.com/berkeley-db/db-4.6.21.tar.gz

    upgrade bzip to 1.0.4
    wget http://www.bzip.org/1.0.4/bzip2-1.0.4.tar.gz

    upgrade openssl to 0.9.9g
    wget http://www.openssl.org/source/openssl-0.9.8g.tar.gz

    It's not convenient to build sqlite-3.5.2, so we just download a binary
    version from it's official site.
    wget http://www.sqlite.org/sqlitedll-3_5_2.zip
    wget http://www.sqlite.org/sqlite-source-3_5_2.zip

    1. more detail on build these libraries
      generally, you can follow the guide in PCbuild/readme.txt. but there
      are thing you need to pay attention to .

    For Tix8.4.2, we should create a python.mak for it, and make a patch on
    makefile.vc. User also need to 'set MSVCDIR=%VCINSTALLDIR%' in cmd
    window.

    For bdb-4.6.21, I can't upgrade dsw to sln with the command:
    devenv db-4.6.21\build_windows\Berkeley_DB.dsw /Upgrade
    instead, open dsw in VS 2005 IDE, convert and save it.

    to build openssl, as the guide said, we can use build_ssl.py in
    PCbuild. but we need to move build_ssl.py, build_ssl.bat and _ssl.mak
    to PCbuild8, and make a little modification.

    1. make pcbuild.sln work properly.
      some options are missed in pcbuild.sln and it's projects. we need to
      edit pyproject.vsprops and etc.

    I can't make make_versioninfo work at first, and then i found that may
    have relationship with SxS(Side by Side, manifest), I run the resource
    wizard and did'nt add resource, but the wizard create resource.h
    and .rc file, after i build the project, it work correctly.

    1. output directory changed
      build python25 in x86 with debug mode, the *.lib, *.dll, *.pyd etc will
      be placed in win32debug. to make build_ssl.py, I calculate the output
      directory add it to LIBPATH.

    Finally, I changed the readme.txt in PCbuild8, so you can follow the
    newer guide.

    @weck weck mannequin added the build The build process and cross-build label Nov 15, 2007
    @tiran
    Copy link
    Member

    tiran commented Nov 15, 2007

    I'm a bit concerned with the upgrade from DB 4.4. to 4.6 and SQLite from
    3.3 to 3.5. Are the APIs backward compatible or can the Python bindings
    handle the new APIs? I believe that Python 2.6 is compatible with db4.6
    but I'm not sure about SQLite. Have you run the unit tests?

    @loewis
    Copy link
    Mannequin

    loewis mannequin commented Nov 15, 2007

    I'm rejecting this patch, for several reasons:

    • it addresses too many issues in a single patch. Separate bug reports
      need to be submitted for independent issues.
    • for each issue, it fails to explain what the problem is. For example,
      "some libraries are outdated" is not a problem per se, but only would be
      a problem if those old libraries don't work with the new compiler; the
      actual problem is not reported here.
    • it suggests to upgrade libraries; I assume it does so for Python 2.6
      and 3.0. However, upgrading libraries should be deferred until before
      the release. People building the development versions of Python are
      expected to arrange the build environment themselves in a way they like,
      using readme.txt only as a guideline.
    • the patches to upgrade the libraries are incomplete.

    @loewis loewis mannequin closed this as completed Nov 15, 2007
    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    build The build process and cross-build topic-installation
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant