Mike Parker wrote:
> Trevor Parscal wrote:
> 
>>
>>
>> yes.. Yay UNIX, BOOO Windows...
>>
> 
> Install Cygwin or MingW + MSYS on Windows and you can do the same thing: ./configure
> make
True, but in the past I have found that cygwin is a poor substitute for the real thing :)

Brad

brad beveridge wrote:
> Mike Parker wrote:
> 
>> Trevor Parscal wrote:
>>
>>>
>>>
>>> yes.. Yay UNIX, BOOO Windows...
>>>
>>
>> Install Cygwin or MingW + MSYS on Windows and you can do the same thing: ./configure
>> make
> 
> True, but in the past I have found that cygwin is a poor substitute for the real thing :)
> 
> Brad
Yes, MSSYS and ctgwin have both been less than satisfying..

besides, compiling on linux / unix isn't what I needed to do with FreeType... I needed to compile it on Windows, for windows... thus..

BOOO Windows... :)

-- 
Thanks,
Trevor Parscal
www.trevorparscal.com
trevorparscal@hotmail.com

Trevor Parscal wrote:

>> I'll feed the freetype2 headers to my C header->D module script,
>> and see what it comes up with. Minus the weirdo macros, that is.
>>
>> But don't hold your breath. ;-)
> 
> I would be VERY interested in seeing what you come up with.. Send me a copy if you can once it is under control, or when you give up...

No go, sorry. There's just too many macros used (worse than SDL!)
So I think you are better off with your hand-translated version ?
(last time I heard, you were still trying to get it to link with
a test C program or something, so that would probably be step one)

I have a similar problem here on Mac OS X, with the "Carbon" headers
that use some C features which makes them hard to port over to D :-(
They work just fine from C, C++, and Objective-C too; but require some
hand-holding to work with D. I've done selected functions, but not all.


Unfortunately, this makes D much less useful - when it can't use C libs.
It's of course doable to write the import modules, just a *lot* of work?
Another problem in this particular case is that they are copyrighted, so
even if I do get them ported I'm not sure I'm allowed to redistribute...

But at least this is one of the "known issues" with the D language.
" These are some of the major bugs:
  Need to write a tool to convert C .h files into D imports. "
(From http://www.digitalmars.com/d/dcompiler.html#general)

--anders

Trevor Parscal wrote:
> OK, so I am still having trouble with this FreeType library, and ... The  people from the FreeType newsgroup told me..
> 
> 
> - do not use the D 'char' for C 'char'. That's because
>   it's default initializer is 0xFF instead of 0, and this
>   will cause all kinds of subtle problems when used
>   naively in D code.
> 
> So what do i use instead? byte? Isn't the intializer the same?
> 
May I ask you why are you using the FreeType library? And also why are you compiling it, is that necessary to use it?

-- 
Bruno Medeiros
Computer Science/Engineering student