couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Cottlehuber <>
Subject Re: [jira] Commented: (COUCHDB-889) improved docs for windows compile from source in INSTALL.Windows
Date Mon, 20 Sep 2010 08:07:36 GMT
Thanks Mark,

Generally I've tried to make this as detailed as possible so any
experienced windows user (NB not programmer) could build from source.
Comments inline.

On 20 September 2010 13:38, Mark Hammond (JIRA) <> wrote:
>    [
> Mark Hammond commented on COUCHDB-889:
> --------------------------------------
> Many of the changes look good, but have the following comments:
> * I wonder if including today's current versions is a good thing - it seems it will just
increase the bitrot in the future.  Can we just default to "latest available" except in the
cases where we know it is not?  If not, then we probably can't justify the existing "latest
available" references either.

I am anticipating updating this for every formal couch release in the
future. But I see your point. So either we:
- confirm exactly what was used & tested for the formal release.
- a range of what is known to work now, and document why somewhere else.

What makes more sense?

Personally, it would have saved me quite a bit of time to know what
level had actually successfully been used, and where to get it, in the
official releases, especially cURL, OpenSSL, & ICU. Maybe this doesn't
need to go in INSTALL.Windows though. Is this a wiki thing?

> * Where is nsis used?

Erlang only. But you need that to get to here. I've send them an
upstream patch which will make a lot of this easier.

> * The inclusion of your entire PATH doesn't seem to add much value either - if the instructions
are correct the path will be correct - so something is redundant.  Less is more when it comes
to busy people trying to get a build up, and the specified "perfect path" will be incorrect
if the retail version of MSVC is used, for example.

OK, I'm happy to remove it, and provide it as wiki or blog post
instead. But it's less accessible. I agree that most people won't need
this, so long as they follow the general notes earlier on.

If you can send me a default path for the retail version that would be
cool, I would like add this to my notes on each environment.

> * Finally, using seamonkey instead of spidermonkey is a fair bit more effort wrt compilation
- it might be reasonable to note that spidermonkey can be used if the reader can decypher
the build instructions, or at least indicate something like "almost all mozilla products will
build the spidermonkey we need (and spidermonkey can, with some difficulty, even be built
stand-alone)  - below are instructions for seamonkey, but get a spidermonkey using whatever
technique you like"

Agreed, but I couldn't find a formal 1.8 release version of
spidermonkey, only RC1. The current INSTALL.Windows refers vaguely to
both & is inconsistent between the URL & the configure:

You will need the following installed:
 * Mozilla SpiderMonkey (1.8) (
and later on:
    ./configure \
        --with-js-include=/cygdrive/c/path_to_seamonkey_include \
        --with-js-lib=/cygdrive/c/path_to_seamonkey_lib \

So INSTALL.Windows should be specific - seamonkey or spidermonkey? Let
me know which one is appropriate & I'll sort it including where to get
it. only has RC1
available. Is that good enough?

>> improved docs for windows compile from source in INSTALL.Windows
>> ----------------------------------------------------------------
>>                 Key: COUCHDB-889
>>                 URL:
>>             Project: CouchDB
>>          Issue Type: Improvement
>>          Components: Build System, Documentation
>>    Affects Versions: 0.11.2, 1.0.1
>>         Environment: Windows only.
>>            Reporter: Dave Cottlehuber
>>             Fix For: 0.11.3, 1.0.2
>>         Attachments: windows_build_from_source_docs.patch
>>   Original Estimate: 0h
>>  Remaining Estimate: 0h
>> ./INSTALL.Windows does not have enough detail to compile from source, due to internet
bit rot.
>> Updates include -
>> - clarification on versions for 32-bit and 64-bit compile setup
>> - using free Microsoft Visual Studio 2008 Express C++ compiler instead of full commercial
>> - improved details on building javascript, libcurl from source
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.

Thanks for your help during sorting this out & the comments above.


View raw message