Missing includes with 1.6 install on win32?

Hi,
Just noticed that when you compile and then ‘nmake install’ ruby 1.6.7 on
win32 with VC++ you don’t get the necessary include files installed in the
destination directory you specify. The DLL and LIB file are put neatly in
the correct spot, so why aren’t the includes?

Paul

Paul E.C. Melis wrote:

Just noticed that when you compile and then ‘nmake install’ ruby 1.6.7 on
win32 with VC++ you don’t get the necessary include files installed in the
destination directory you specify. The DLL and LIB file are put neatly in
the correct spot, so why aren’t the includes?

Did you look under:

%DESTDIR%\lib\ruby\1.6\i586-mswin32

That’s where they should have been installed.

“Lyle Johnson” lyle@users.sourceforge.net wrote in message
news:3D7FF789.2010408@users.sourceforge.net

Paul E.C. Melis wrote:

Just noticed that when you compile and then ‘nmake install’ ruby 1.6.7
on

win32 with VC++ you don’t get the necessary include files installed in
the

destination directory you specify. The DLL and LIB file are put neatly
in

the correct spot, so why aren’t the includes?

Did you look under:

%DESTDIR%\lib\ruby\1.6\i586-mswin32

That’s where they should have been installed.

Hmmm, ok, that’s where they are located indeed. But why all the way down
there?

Paul

Hi,

···

At Thu, 12 Sep 2002 17:19:46 +0900, Paul E.C. Melis paul@floorball.nl wrote:

Did you look under:

%DESTDIR%\lib\ruby\1.6\i586-mswin32

That’s where they should have been installed.

Hmmm, ok, that’s where they are located indeed. But why all the way down
there?

config.h depends on platform, so in order to avoid spattering
headers.

Do you think it should be installed separated from the other
common headers?


Nobu Nakada

So you can have a ruby installation sitting on a network drive with
multiple computer architectures pulling from the same ruby library
DESTDIR. The shared libraries are arch specific. The windows pentium
machine will look in i586-mswin32, a linux machine would look in
i386-linux (or i586 depending on optimization I think), and so forth.

···

On Thu, Sep 12, 2002 at 05:19:46PM +0900, Paul E.C. Melis wrote:

“Lyle Johnson” lyle@users.sourceforge.net wrote in message
news:3D7FF789.2010408@users.sourceforge.net

Did you look under:

%DESTDIR%\lib\ruby\1.6\i586-mswin32

That’s where they should have been installed.

Hmmm, ok, that’s where they are located indeed. But why all the way down
there?

Paul


Alan Chen
Digikata LLC

nobu.nokada@softhome.net wrote in message
news:200209120950.g8C9oGQ17734@sharui.nakada.kanuma.tochigi.jp

Hi,

Did you look under:

%DESTDIR%\lib\ruby\1.6\i586-mswin32

That’s where they should have been installed.

Hmmm, ok, that’s where they are located indeed. But why all the way down
there?

config.h depends on platform, so in order to avoid spattering
headers.

Do you think it should be installed separated from the other
common headers?

Well, if only config.h is platform-dependent, then I would put the rest in a
general /include dir, although I don’t see an easy solution for
making sure the right config.h is used depending on the architecture in
question.

···

At Thu, 12 Sep 2002 17:19:46 +0900, > Paul E.C. Melis paul@floorball.nl wrote:

Hi,

config.h depends on platform, so in order to avoid spattering
headers.

Do you think it should be installed separated from the other
common headers?

Well, if only config.h is platform-dependent, then I would put the rest in a
general /include dir,

Maybe include/ruby-$(version) directory, and config.h also
should be in $(arch) directory under there.

although I don’t see an easy solution for
making sure the right config.h is used depending on the architecture in
question.

rbconfig.rb knows.

···

At Fri, 13 Sep 2002 01:40:39 +0900, Paul E.C. Melis paul@floorball.nl wrote:


Nobu Nakada