Re: Yet another Windows installer
- From: Luis Lavena <luislavena@xxxxxxxxx>
- Date: Thu, 20 Mar 2008 06:47:36 -0700 (PDT)
On Mar 20, 9:27 am, Michal Suchanek <hramr...@xxxxxxxxxx> wrote:
On 18/03/2008, Luis Lavena <luislav...@xxxxxxxxx> wrote:
On Mar 16, 2:12 pm, Phillip Gawlowski <cmdjackr...@xxxxxxxxxxxxxx>
wrote:
> (IMHO, it might be a great idea to switch to a more recent version of
> Visual C all together, considering that the Express Edition is free, and
> can produce non-/NET code, but that's just my opinion).
Jumping late on this thread (been away in vacation trip).
Switching to VC8/VC9 or even VC7 requires recompilation of
dependencies to use the same CRT DLL. Search the list for posts about
this.
Been raised before, tried several times, and is impossible to
accomplish without loosing your brain in the process.
I think I will move the MinGW+MSYS building process one step further
and use the better Windows alternatives than traditional dependencies
(like win_iconv that _why commented previously).
You're welcome to join us at One-Click Installer Developement List
(http://rubyforge.org/mailman/listinfo/rubyinstaller-devel).
As Mailman does not like my email address ( I don't know why but
Mailmen refuse to communicate with me at all) I will send the results
of trying to use the install3 zip archive here.
Weird, are you already registered to other mailing lists in rubyforge?
- there is no script for running the rake task(s), and it might not be
obvious how to run them for people who are not familiar with rake yet.
Well the idea of installer3 is not being used by end-users, but by
developers of Ruby on Windows as "safe bootstrap" that can be
recreated from scratch without huge list of depepdencies to be
manually download, set and everything.
The idea is "Use as much ruby as possible", that means use Rake. We
need some Documentation Love :-)
- there is no default rake action, and one has to look into the
recipes to find out what are the available actions (download, unpack,
configure, compile, install)
I didn't add one since was playing with the dependencies recipes. I'm
still not convinced this is the best layout for the code, and even
less for the actions I'm performing.
On the original post I commented the task sequence, but since there is
no documentation... :-$
- rake aborts download action due to execution timeout - probably
depends on download speed
Yeah, Sourcefor servers often timeout, no other alternative than "try
again".
- bsdtar requires zlib1.dll which is not downloaded. This is not
normally present in the system although it might be present if you put
your ruby installation into PATH.
I have a exerb "rake.exe" that weights 600K and is the only executable
I need to bootstrap ruby (without requiring a previous ruby
installation). But if you plan to
-there is some sort of error with directories. It appears the scripts
fail to create sandbox/ruby_build, and running configure fails because
the configure script is not found although it appears to be present.
That's because the task sequence is not performed as defined
originally. Can you provide the steps to recreate? maybe a task is
missing the directory as dependency.
Thanks
No, thank you for your time and comments!
Hope you can workaround the mailman issues (or mail directly to
rubyforge staff) and we can collaborate further.
Regards,
--
Luis Lavena
.
- Follow-Ups:
- Re: Yet another Windows installer
- From: Michal Suchanek
- Re: Yet another Windows installer
- References:
- [ANN] Yet another Windows installer
- From: Phillip Gawlowski
- Re: [ANN] Yet another Windows installer
- From: James Tucker
- Re: [ANN] Yet another Windows installer
- From: Phillip Gawlowski
- Re: [ANN] Yet another Windows installer
- From: James Tucker
- Re: [ANN] Yet another Windows installer
- From: Phillip Gawlowski
- Re: Yet another Windows installer
- From: Luis Lavena
- Re: Yet another Windows installer
- From: Michal Suchanek
- [ANN] Yet another Windows installer
- Prev by Date: Re: how to get inherited class names ?
- Next by Date: if-less if statements
- Previous by thread: Re: Yet another Windows installer
- Next by thread: Re: Yet another Windows installer
- Index(es):
Relevant Pages
|