wanted: buildslave that uses a Microsoft compiler #230
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#230
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It would be nice to have a buildslave that does not have GCC installed and in which everything is built using a Microsoft compiler.
A good candidate for which Microsoft compiler would be Visual Studio .NET 2003 -- this is the version of the Microsoft compiler that Python 2.4 and Python 2.5 are built with. On the other hand, this version of the Microsoft compiler is no longer distributed by Microsoft so it can be inconvenient or expensive to acquire.
Another reasonable candidate would be Visual Studio 2008 Express Edition -- this is likely to be the compiler used to build Python 2.6 and Python 3.0. However, to use VS8 you probably have to build the current python svn trunk yourself from source using VS8 instead of using the precompiled Python 2.5.1.
Another reasonable candidate is "whatever Microsoft compiler is easiest for you to use".
As for operating system, I personally would choose for this buildslave to be running Windows XP rather than Windows Vista, but that is mainly because I am hoping that Microsoft will give up and withdraw Vista from the market. Whoever actually implements this task should probably use whichever Microsoft operating system will be easiest for them.
Apropos the choice of Vista or XP, here is a nice review from a programmer who upgraded from Vista to XP and was very pleased at the many new features that XP offers.
http://dotnet.org.za/codingsanity/archive/2007/12/14/review-windows-xp.aspx
I say that we're definitely going to want this eventually, so I'm moving it from "undecided" to "eventually" Milestone. (Feel free to tell me if you think otherwise!)
We have such a machine available now -- the one named "Windows with Native Python and Microsoft compiler -- no cygwin Python and no gcc", and located at virtual2.allmydata.com:33891 . However, we're not currently using it to build and test Tahoe.
Dcoder's buildslave has MSVC++, but is not currently working due to #1073.
Dcoder's buildbot uses MSVC++ from Visual Studio 9.0 (a.k.a. Visual Studio 2008) on 64-bit Windows 7.