From owner-freebsd-questions Tue Jun 25 3:52:21 2002 Delivered-To: freebsd-questions@freebsd.org Received: from grillolja.cs.umu.se (grillolja.cs.umu.se [130.239.40.17]) by hub.freebsd.org (Postfix) with ESMTP id 215ED37B404 for ; Tue, 25 Jun 2002 03:52:13 -0700 (PDT) Received: from gren.cs.umu.se (gren.cs.umu.se [130.239.40.187]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by grillolja.cs.umu.se (Postfix) with ESMTP id 3600A9FD7; Tue, 25 Jun 2002 12:52:12 +0200 (MEST) Date: Tue, 25 Jun 2002 12:52:11 +0200 (MEST) From: Paul Everlund To: =?iso-8859-1?q?Gavin=20Kenny?= Cc: Martin Klaffenboeck , Subject: Re: Porting Tips In-Reply-To: <20020625104100.72418.qmail@web20003.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 25 Jun 2002, Gavin Kenny wrote: > --- Martin Klaffenboeck > wrote: > Am Di, 2002-06-25 um 11.23 schrieb Gavin > Kenny: > > > Hi Guys, > > > > > > I'm going to have a go at porting the VideoLan > > > Server to FreeBSD. It was written for Linux and > > > there is a Darwin (Mac OS) port, so I'm kinda > > > hoping it shouldn't be too hard (famous last > > > words). > > > > > > I never written anything for FreeBSD, so what > > > should I look out for? Any good pointers, tips, > > > different naming conventions for libraries etc > > > or better still HOW-TO's, would be really useful. > > > > Do you know the Porters Handbook? > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ > > > > Martin > > I have had a look at it but it seems more concerned in > building a FreeBSD Port (a fantastic invention by the > way ;-) rather than how to take a piece of software > that was written for Linux (or any other operating > system) and getting it to compile and run on FreeBSD. > Am I being naive? > > Gavin Have "ported" some applications to FreeBSD that where meant for Linux and Solaris. What I did was compiling the code with a lot of warning options turned on, then fixing errors as they did appear. One was for example O_SYNC to O_FSYNC. In the end it did run ok! Not a "nice" way of porting applications I guess, but it has worked for me. :-) Good luck! Best regards, Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message