Re: Important changes in Docwriter
A quick tip: If search does not work for you while browsing the docs locally, try running `mkdocs serve' (or `python3 -m mkdocs serve') in the `docs/' directory (after `make refdoc'). This serves the site on a local server, providing a more website-like experience.
Re: FreeType docs not correctly built if srcdir != builddir
Hello Werner, > if `srcdir` == `builddir`, the directory > > $srcdir/docs/reference/images > > exists after executing `./configure && make && make refdoc`, and the > 'FT' icon is properly displayed. However, if `srcdir` != `builddir`, > the directory is missing, and the icon doesn't get displayed. The static assets were moved one directory up in 237fed6, causing the copy to fail. Fixed in master now, please check! Nikhil
Re: tracing and logging library - GSOC Project
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 projects have to do to support us vs. Linux/BSD platforms, so hopefully "standard Unix environments" will cover us too. -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Engineering - https://blogs.oracle.com/alanc
Re: tracing and logging library - GSOC Project
> 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 GNU/Linux or BSD variants. 'macOS' and 'iOS' are more or less based on BSD, while 'ChromeOS' is a GNU/Linux variant (to a certain extent). 'ReactOS' should essentially use the same API as Windows. > Further, I have query related to the testing part of the project. I > know the basic testing will be surely part of this project. But > just wanted to check the scope of testing that is required as part > of this project on these platforms. Is there any support for > different test environments already available? We don't have CI (yet). Werner
FreeType docs not correctly built if srcdir != builddir
Nikhil, if `srcdir` == `builddir`, the directory $srcdir/docs/reference/images exists after executing `./configure && make && make refdoc`, and the 'FT' icon is properly displayed. However, if `srcdir` != `builddir`, the directory is missing, and the icon doesn't get displayed. Please check that. Werner
Re: Important changes in Docwriter
> Docwriter 1.3 has been released. This release, along with commit > 1fd3148 includes important changes to support Python >= 3.5 and drop > support for older versions. [...] Thanks a lot for updating FreeType accordingly! Werner
Re: tracing and logging library - GSOC Project
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 part of this project. But just wanted to
check the scope of testing that is required as part of this project on
these platforms.
Is there any support for different test environments already available?
Thank you...
On Sun, Mar 22, 2020 at 12:46 PM Werner LEMBERG wrote:
>
> > 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
> >- BeOS
> >- Mac
> >- Symbian
>
> The above are more or less dead. ('Mac' here means the old, non-Unix
> OS.)
>
> >- OS2
> >- OpenVMS
>
> These two platforms are a bit less dead :-) However, you don't have
> to take special care for them.
>
> >- Windows
>
> Windows is important and one of main reasons for contemplating on the
> use of a logging library, since on that platform GUI programs can't
> send stderr output to the console.
>
> Note that I would like to have a fallback to stderr in case a logging
> library is not available.
>
>
> Werner
>
Re: tracing and logging library - GSOC Project
> 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
>- BeOS
>- Mac
>- Symbian
The above are more or less dead. ('Mac' here means the old, non-Unix
OS.)
>- OS2
>- OpenVMS
These two platforms are a bit less dead :-) However, you don't have
to take special care for them.
>- Windows
Windows is important and one of main reasons for contemplating on the
use of a logging library, since on that platform GUI programs can't
send stderr output to the console.
Note that I would like to have a fallback to stderr in case a logging
library is not available.
Werner
Re: tracing and logging library - GSOC Project
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 - ChromeOS - ReactOS - Ghostscript Further going through the codebase I also found out that following platforms are also supported by FreeType: - Amiga - Atari - BeOS - Mac - OS2 - Symbian - OpenVMS - Windows This seems to be a long list and hence I wanted to confirm the platforms that are actively supported and are under the scope of this project. Thank You... On Wed, Mar 4, 2020 at 3:02 AM Priyesh kumar wrote: > *>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, however; maybe this needs some extra work.* > > I will definitely look into the windows library... > > Thanks... > > On Wed, Mar 4, 2020 at 1:30 AM Werner LEMBERG wrote: > >> >> 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 >> project! Right now you should do some preliminary investigations only >> so that you are able to write a useful proposal. >> >> [If you want to work on that project without being part of GSoC this >> would be nice too and very welcomed, of course.] >> >> That said, `zlog` looks indeed promising. Not sure about the Windows >> port, however; maybe this needs some extra work. >> >> > Please guide me if I am working in right direction.. >> >> You are :-) >> >> >> Werner >> >
