Re: about folder naming (Re: Updates on Freetype Demos - Swift Support)

[suzuki toshiya]

If we are working with Darwin kernel plus open source components provided by
Apple, using "darwin" name might be a considerable option, because there had
been the projects like OpenDarwin, PureDarwin, etc. But we are not - we are
working with Swift (or Objective-C) and Cocoa. Darwin is not good name for
the directory to store Cocoa-specific components, I think. Anyway thank you
for reminding the name of the kernel.

Regards,
mpsuzuki

On 2024/06/24 11:42, Hin-Tak Leung wrote:
> FWIW, the OS identification for mac os x (I believe the mac stuff was pre- os x) is 
> "darwin". Like the cross-compiler is x86-64-apple-darwinN-gcc . c.f. 
> x86_64-redhat-linux-gcc, etc.
>
> N is 14 currently, I think.
>
> On Sunday 23 June 2024 at 22:53:11 BST, suzuki toshiya 
> <mpsuzuki@hiroshima-u.ac.jp> wrote:
>
>
> I agree with Alex suggestion "do not touch mac/ folder, but add new folder,
> like cocoa/". I'm afraid the lifetime of Cocoa might be shorter than GDI
> (although Cocoa is younger than GDI), the naming like "mac/" for Cocoa is
> not the best option.
>
> Regards,
> mpsuzuki
>
> P.S.
> mac/cocoa/ might be acceptable, but slightly too complex.
>
> On 2024/06/23 23:21, Alexei Podtelezhnikov wrote:
> > > Also, there is a mac folder (grmac.c) inside of the graph.
> > > As I tested, it is not in use in my machine. Apps are working fine without it.
> > > Should remain it?
> >
> > The mac/ folder contains legacy macos 7-9 support. It is untested and
> > probably broken.
> > I suggest that you create a new subfolder cocoa/, for example. BTW, it
> > does not have to support `make`.
> > Whatever works natively. Given that the main src/ programs are pure C,
> > it is more important that your implementations of
> > gr_cocoa_device_init(), gr_cocoa_surface_init() are compatible with C
> > and can be compiled. Perhaps, Objective-C is all you need.
> >
> > Alexei