search

mcspring / googletest

Automatically exported from code.google.com/p/googletest
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Installation directory should be /usr/local/lib64 on 64 bit systems #328

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. make install

What is the expected output? What do you see instead?
Actual: installation in /usr/local/lib 
Expected: installation in /usr/local/lib64 

What version of Google Test are you using? On what operating system?
Google Test: 1.5.0
OS: Centos 5.5

Please provide any additional information below, such as a code snippet.
Configuration script doesn't allow changing the installation directory and 
gives the message:
libtool: install: error: cannot install `lib/libgtest_main.la' to a directory 
not ending in /usr/local/lib

Original issue reported on code.google.com by andrea.s...@gmail.com on 28 Oct 2010 at 3:55

GoogleCodeExporter commented 9 years ago 
We have dropped support for 'make install' in 1.5 (see the CHANGES file, and 
the FAQ in the wiki for explanations).

We will accept a patch for this, though. If you decide to submit one, see 
http://code.google.com/p/googletest/wiki/DevGuide#Contributing_Code for how to 
contribute a patch. And it will still be up to the community to support this 
functionality.

Original comment by vladlosev on 29 Oct 2010 at 3:48

GoogleCodeExporter commented 9 years ago 
Actually, we plan to remove the 'install' make target entirely.  Therefore a 
patch wouldn't make much sense as it will be undone anyway.

See 
http://code.google.com/p/googletest/wiki/FAQ#Why_is_it_not_recommended_to_instal
l_a_pre-compiled_copy_of_Goog for why we decided to do that.

Original comment by w...@google.com on 29 Oct 2010 at 4:54

GoogleCodeExporter commented 9 years ago 
Given continued demand for this feature, I think we should not delete it. We 
can leave it in unsupported.

Original comment by vladlosev on 29 Oct 2010 at 5:26

GoogleCodeExporter commented 9 years ago 
demand != what we should do

Original comment by w...@google.com on 29 Oct 2010 at 5:29

GoogleCodeExporter commented 9 years ago 
To elaborate, there will *always* be demand on deprecated features.  That 
doesn't mean we should support them indefinitely.

Original comment by w...@google.com on 29 Oct 2010 at 5:33