On 3/22/20 7:58 AM, Werner LEMBERG wrote:
Instead of 'Linux' (which is just an OS kernel) I would rather ask for
'standard Unix environments' like GNU/Linux or BSD variants.
Thanks - we're still shipping FreeType in Solaris as well, but are trying
to reduce the number of things that FOSS
> As per the reply, my main focus for this project will be on the
> following platforms:
>
>- Windows
>- macOS
>- Linux
>- iOS
>- ChromeOS
>- Android
>- ReactOS
Instead of 'Linux' (which is just an OS kernel) I would rather ask for
'standard Unix environments' like
Thanks for the reply,
As per the reply, my main focus for this project will be on the
following platforms:
- Windows
- macOS
- Linux
- iOS
- ChromeOS
- Android
- ReactOS
Further, I have query related to the testing part of the project. I know
the basic testing will be surely
> It seems according to the FreeType official website support the
> following platforms: [...]
>
>- Ghostscript
This is not a platform per se.
> Further going through the codebase I also found out that following
> platforms are also supported by FreeType:
>
>- Amiga
>- Atari
>
Hi,
I was trying to make the list of platforms on which logger needs to be
enhanced so that I could find the logging library as per the requirement
for my proposal. It seems according to the FreeType official website
support the following platforms:
- GNU/Linux
- iOS
- Android
-
*>Hold your horses – what you do currently is already part of the GSoC*
*>project! Right now you should do some preliminary investigations only*
*>so that you are able to write a useful proposal.*
Got it! :)
*>That said, `zlog` looks indeed promising. Not sure about the Windows*
*>port,
Hello Priyesh,
> Working forward in an external library hunt i came across two
> C based logging libraries: [...]
>
> I am also working on a prototype that will print log messages
> generated by FT_ERROR into a log file.
Hold your horses – what you do currently is already part of the GSoC
Hey,
Working forward in an external library hunt i came across two C based
logging libraries:
1.log4c
2.zlog
In the above mentioned libraries zlog claims to be faster, more safer and
powerful.
It is also well tested and mature, it also has a windows version.
Some of zlog's features which i think
*>In other words, my gut feeling says no to the idea of using any>different
code language. The logging facility should be written in>the C language,
too, not using more recent features than C99 so that>older compilers
support it.*
Got it!! Thanks for your suggestion... I will keep this in mind.
Hello Priyesh!
Thanks for your interest in FreeType.
>[...] Therefore, I propose to implement separate code files for
>logging, which could be based on C++ and can be easily plugged
>into the existing C code base. In addition to this, improving a
>bit on documentation can
Hi ,
I am Priyesh , currently pursuing B.Tech in Computer Science at Indian
Institute of Information Technology Una , India . Currenlty, I am a third
year student and interested in working on Freetype's GSOC Project -* "**Replace
FreeType's tracing and debugging facilities with an external logging
[Sorry for the very late reply. I had to prepare a conference and a
concert, and I took a vacation, too, with limited e-mail access.]
> Hi, I am interested in doing the project, “Replace FreeType's
> tracing and debugging facilities with an external logging library.”
> Is this still open for
Hi, I am interested in doing the project, Replace FreeType's tracing and
debugging facilities with an external logging library. Is this still open
for work this year?
13 matches
Mail list logo
