This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Any current plans for an SDL package?


At 04:40 PM 11/23/2003, unknown_kev_cat@hotmail.com you wrote:
>Christopher Faylor wrote:
>>On Fri, Nov 21, 2003 at 08:24:50PM -0500, unknown_kev_cat@hotmail.com wrote:
>>
>>>I am wondering if anybody currently plans to create an SDL mingw32 binary package for cygwin. As it is currently hard to compile SDL, having this package, (and SDL-image and SLD-mixer, 2 other libs that are usually used with sdl, that may even be harder to compile) would be of help to many ppl. If nobody plans on creating such a package i may be able to, however i warn you now: i do not intend on become a cygwin package maintaner.
>>
>>The mingw web page is at: http://www.mingw.org/ .  If you are interested
>>in a mingw package, that is the place to look.
>
>I belive I was misunderstood. I was asking about/offering to build a Cygwin SDL Binary package. I only mentioned mingw32 as that appears to be the way SDL is normally built under cygwin. AFAIK Mingw32 library binaries can be linked with cygwin binaries with little trouble so making the package be a mingw32 binary would be ideal. SDL is fairly hard to setup under Cygwin, especially as some libraries that cygwin comes with are needed by SDL, yet the headers are not availble for install via the setup program, you have to copy them over from the library sources by hand.


Can you enumerate these libraries and give details about what's needed?
If are files that should be in, say a <package>-devel package rather than
just the source package, that is good feedback. 


>So to sum it up: A SDL Libray Binary package, probably compiled using mingw32, (actaully using cygwin's gcc with '-mno-cygwin'), intended for  use under cygwin when compiling open source games.


While this sounds useful, I don't think it falls in the category of a Cygwin
package.  Packages offered with setup depend on cygwin1.dll in some form.  
What you're describing above doesn't fit this mold.  I think that's what 
Chris was trying to point out.  This would be a good package for this list 
to know about even if it doesn't target Cygwin though.


>I could also try to compile a Cygwin binary version of the library, but that would be at least slightly harder.


This would be a true Cygwin package so I don't see a reason it couldn't be 
included in setup if it passes successfully through the ITP stage.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]