Date: Fri, 28 Dec 2007 16:07:11 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Rob Belics <rob_belics@charter.net> Cc: freebsd-ports@freebsd.org Subject: Re: Porting Windows program datatype problem Message-ID: <20071228050711.GV40785@server.vk2pj.dyndns.org> In-Reply-To: <4773E79B.1090904@charter.net> References: <4773E79B.1090904@charter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--vni90+aGYgRvsTuO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 27, 2007 at 11:57:47AM -0600, Rob Belics wrote: >There is a Windows open source program I would like to port to FreeBSD. I= t=20 >seems to compile OK, using gcc, but chokes on MS/Windows only type data=20 >types like 'ulong'. What would be the easiest way to fix/convert these, o= r=20 >must it be done manually? I suspect your only option is "manually". Your best approach might be a set of Windows headers and something like ctags or id-utils to let you quickly search for the type you want to see how it's defined. Note that I also agree that Dmitry's approach is likely to be the best/easiest. Since 'sed' can't easily match C tokens, automated attempts to use sed are highly likely to unintentionally mangle innocent character strings that just look like data types. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --vni90+aGYgRvsTuO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHdIR//opHv/APuIcRAkIDAKCVyZpZ9XYIWjD++6Y2Jx2Z3/FergCeN+UO GwMQRfTbtMKgJUgLBMWQeIQ= =tK4r -----END PGP SIGNATURE----- --vni90+aGYgRvsTuO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071228050711.GV40785>