ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-20 21:43:09 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
6e8fe30859
tahoe-lafs/windows/setup.py

84 lines
1.7 KiB
Python
Raw Normal View History

first stab at windows build details. there are many and various fiddly details that were involved in this process on mountain view. This is a stripped down version of the build process used there. there's hence a good chance that one or two necessary details got stripped down through the cracks. this provides a py2exe setup.py to build a tahoe.exe and a tahoesvc.exe the former is equivalent to bin/tahoe, but without the start/stop commands. the latter is a windows service that instantiates a client whose basedir is found in the registry.
2008-01-10 02:01:56 +00:00
from distutils.core import setup
import py2exe
add files from allmydata/web to py2exe distribution when building the py2exe package, glob src/allmydata/web/* into web/ within the dist
2008-01-10 22:34:46 +00:00
import glob
add confwiz to py2exe build including setting up the windows xp look and feel stuff.
2008-01-12 01:42:27 +00:00
lnf_manifest = """
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity
version="0.64.1.0"
processorArchitecture="x86"
name="Controls"
type="win32"
/>
<description>%s</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>
"""
tweak py2exe setup.py to link in xmlplus iff present so in the build slave's environment, everything builds and runs fine without '_xmlplus'. In my existing local environment everything builds and runs only if I tell py2exe to explicitly link in '_xmlplus'. the _xmlplus module, tested for by the python standard library, comes from PyXML ( http://pyxml.sf.net ) a project which is no longer maintained and, for instance, hasn't released a build for windows past python 2.4 hence something about the way nevow and the std lib import xml dependencies causes build environment incompatabilities between my box (which is running py24 currently) and the buildslave (which is on py25, and doesn't have PyXML) (if I remove _xmlplus from my environment, then a different set of nevow/xml import problems emerge, which do not occur in the buildslave's py25 env) this change tests the environment the build is happening in, and if the _xmlplus package is importable, then py2exe is directed to link it into the build. otherwise the package is left out. as far as I comprehend the issue this should make both of these environments work. if other people have problems around this issue, obviously I'm interested in learning more.
2008-01-15 23:59:41 +00:00
packages = ['encodings']
try:
import _xmlplus
except ImportError:
pass
else:
packages.append('_xmlplus')
add confwiz to py2exe build including setting up the windows xp look and feel stuff.
2008-01-12 01:42:27 +00:00
first stab at windows build details. there are many and various fiddly details that were involved in this process on mountain view. This is a stripped down version of the build process used there. there's hence a good chance that one or two necessary details got stripped down through the cracks. this provides a py2exe setup.py to build a tahoe.exe and a tahoesvc.exe the former is equivalent to bin/tahoe, but without the start/stop commands. the latter is a windows service that instantiates a client whose basedir is found in the registry.
2008-01-10 02:01:56 +00:00
setup_args = {
'name': 'Tahoe',
'description': 'Allmydata Tahoe distributated storage',
'author': 'Allmydata, Inc.',
'windows': [
add confwiz to py2exe build including setting up the windows xp look and feel stuff.
2008-01-12 01:42:27 +00:00
{
'script': 'confwiz.py',
'icon_resources': [(1, 'amdicon.ico')],
'other_resources': [(24,1,lnf_manifest%'Allmydata Tahoe Config Wizard')],
},
first stab at windows build details. there are many and various fiddly details that were involved in this process on mountain view. This is a stripped down version of the build process used there. there's hence a good chance that one or two necessary details got stripped down through the cracks. this provides a py2exe setup.py to build a tahoe.exe and a tahoesvc.exe the former is equivalent to bin/tahoe, but without the start/stop commands. the latter is a windows service that instantiates a client whose basedir is found in the registry.
2008-01-10 02:01:56 +00:00
],
'console': [
'tahoe.py',
],
'service': [
'tahoesvc',
],
'data_files': [
('.', [
],),
add files from allmydata/web to py2exe distribution when building the py2exe package, glob src/allmydata/web/* into web/ within the dist
2008-01-10 22:34:46 +00:00
('web', glob.glob('../src/allmydata/web/*')),
add winfuse plugin to installer this adds the latest build of mike's winfuse plugins, now also running as a windows service (and using the node.url, private/root_dir.cap files from the noderoot specified by the registry) into the install process.
2008-01-17 02:15:35 +00:00
('winfuse', glob.glob('./winfuse/*')),
first stab at windows build details. there are many and various fiddly details that were involved in this process on mountain view. This is a stripped down version of the build process used there. there's hence a good chance that one or two necessary details got stripped down through the cracks. this provides a py2exe setup.py to build a tahoe.exe and a tahoesvc.exe the former is equivalent to bin/tahoe, but without the start/stop commands. the latter is a windows service that instantiates a client whose basedir is found in the registry.
2008-01-10 02:01:56 +00:00
],
'zipfile' : 'library.zip',
'options': {
"py2exe": {
"excludes": [
fix nevow build prob for py2exe nevow attempts to use pkg_resources to find the formless css file upon import, if pkg_resources is available. unfortunately using pkg_resources to find files is not supported if the files are being loaded from a zip archive (i.e. only source and egg), and further py2exe uses a zip bundle for all the code and dependent libraries. hence having both pkg_resources and nevow built into an exe causes nevow to explode upon import. this tells py2exe not to link pkg_resources into the target, so that this behaviour isn't stimulated. the side effect being that pkg_resources isn't available.
2008-01-10 22:26:19 +00:00
"pkg_resources",
first stab at windows build details. there are many and various fiddly details that were involved in this process on mountain view. This is a stripped down version of the build process used there. there's hence a good chance that one or two necessary details got stripped down through the cracks. this provides a py2exe setup.py to build a tahoe.exe and a tahoesvc.exe the former is equivalent to bin/tahoe, but without the start/stop commands. the latter is a windows service that instantiates a client whose basedir is found in the registry.
2008-01-10 02:01:56 +00:00
],
"includes": [
],
tweak py2exe setup.py to link in xmlplus iff present so in the build slave's environment, everything builds and runs fine without '_xmlplus'. In my existing local environment everything builds and runs only if I tell py2exe to explicitly link in '_xmlplus'. the _xmlplus module, tested for by the python standard library, comes from PyXML ( http://pyxml.sf.net ) a project which is no longer maintained and, for instance, hasn't released a build for windows past python 2.4 hence something about the way nevow and the std lib import xml dependencies causes build environment incompatabilities between my box (which is running py24 currently) and the buildslave (which is on py25, and doesn't have PyXML) (if I remove _xmlplus from my environment, then a different set of nevow/xml import problems emerge, which do not occur in the buildslave's py25 env) this change tests the environment the build is happening in, and if the _xmlplus package is importable, then py2exe is directed to link it into the build. otherwise the package is left out. as far as I comprehend the issue this should make both of these environments work. if other people have problems around this issue, obviously I'm interested in learning more.
2008-01-15 23:59:41 +00:00
"packages": packages,
first stab at windows build details. there are many and various fiddly details that were involved in this process on mountain view. This is a stripped down version of the build process used there. there's hence a good chance that one or two necessary details got stripped down through the cracks. this provides a py2exe setup.py to build a tahoe.exe and a tahoesvc.exe the former is equivalent to bin/tahoe, but without the start/stop commands. the latter is a windows service that instantiates a client whose basedir is found in the registry.
2008-01-10 02:01:56 +00:00
#"optimize" : 2,
},
},
}
if __name__ == '__main__':
setup(**setup_args)
_junk = py2exe # appease pyflakes
del _junk
Reference in New Issue Copy Permalink