Difference between revisions of "Talk:Win32CompileMSYSNew"

From VideoLAN Wiki
Jump to navigation Jump to search
 
(11 intermediate revisions by 3 users not shown)
Line 6: Line 6:
 
--[[User:Mcross|Mcross]] 18:55, 20 July 2009 (UTC)
 
--[[User:Mcross|Mcross]] 18:55, 20 July 2009 (UTC)
  
When I installed msys, from the msys prompt, /usr/ is equivalent to C:\msys\1.0\, so wherever you see /usr/win32/, I had to use /win32/
+
(Fixed)
 +
 
 +
When I installed msys, from the msys prompt, /usr/ is equivalent to C:\msys\1.0\, so wherever you see jb refer to  /usr/win32/, I had to use only /win32/
 +
 
 +
(noted)
 +
 
 +
I also needed to get and build a recent x264 snapshot (latest trunk needs >0.76).
 +
 
 +
--Simonh 29 Sept 2009
 +
 
 +
*'''Fix libtool search dirs''', seem incorrect.
 +
 
 +
--[[User:Diblo Dk|Diblo Dk]] 22:56, 14 June 2010 (UTC)
 +
 
 +
What looks incorrect? Did it cause failures? (I think it just looks odd but is right) [[User:Rogerdpack|Rogerdpack]] 21:27, 21 September 2010 (UTC)

Latest revision as of 21:29, 21 September 2010

The links to update autoconf, automake, and libtool seem incorrect - they install into /usr/local and contain executables named with the version number (as in 'autoconf-2.61'). The MSYS versions seem to work better, as in:

--Mcross 18:55, 20 July 2009 (UTC)

(Fixed)

When I installed msys, from the msys prompt, /usr/ is equivalent to C:\msys\1.0\, so wherever you see jb refer to /usr/win32/, I had to use only /win32/

(noted)

I also needed to get and build a recent x264 snapshot (latest trunk needs >0.76).

--Simonh 29 Sept 2009

  • Fix libtool search dirs, seem incorrect.

--Diblo Dk 22:56, 14 June 2010 (UTC)

What looks incorrect? Did it cause failures? (I think it just looks odd but is right) Rogerdpack 21:27, 21 September 2010 (UTC)