Re: logging support ready for integration into master

Hello Werner, *> Fixed, thanks, and force-pushed! Please test.* I have tested the changes with the demo programs and it is working fine now.. : D Thanks, Priyesh On Fri, Dec 4, 2020 at 8:52 PM Werner LEMBERG wrote: > > > Which commit (from your GSoC branch) are you referring to? > > > > The

Re: logging support ready for integration into master

Hi Werner, *> I've incorporated your patch into the corresponding commit, then doing> a `git push -f`.* Ok, Great !! *> Which commit (from your GSoC branch)* *> are you referring to?* The changes in `include/freetype/internal/ftdebug.h' in commit: 802176853b5418d34704f1705617333145410625 (link

Re: logging support ready for integration into master

Hi Werner, Thanks for doing the additions. The code is looking much cleaner now : D The updated code is working fine when we are using the `FT2_DEBUG' environment variable with tags(-v / -t / -vt), but without these tags I am getting corrupted memory issue with the `features_buf' char array in

Re: Logging Library-GSOC

Hi Werner, I have written the Final Report for my project @here Please take a look at it and provide feedback... Thanks, Priyesh

Re: Logging Library-GSOC

Hi Werner, *> * I wonder whether it is necessary to have a separate `dlg.vcxproj`> file (and friends). What about folding its contents into> `freetype.vcxproj`? The `dlg` stuff gets completely integrated into> FreeType and will be always linked statically...* So, I have updated the code in

Re: Logging Library-GSOC

Hi, *> Create a new branch that presents your code in an ordered fashion,> this is, using not-too-large, concise, well documented commits>that makes it easy to understand how your project works. Have a>look how Anuj is doing this to get an idea.>While doing so, please check

Re: Logging Library-GSOC

riyesh On Wed, Aug 19, 2020 at 12:39 AM Vincent Torri wrote: > Hello, > > On Tue, Aug 18, 2020 at 1:03 PM Priyesh kumar > wrote: > > > > Hi Werner, > > I was trying to compile FreeType on Windows using Cygwin and I was > > getting the following error wh

Re: Logging Library-GSOC

*> IMHO it's not worth that you examine this in more detail**.* Ok... *> No idea. What exactly are you interested in?* I have tested the changes on OS X using Autotools i.e by using: *sh autogen.sh* *./configure* *make* I know FreeType mainly uses Autotools for building purposes and here I

Re: Logging Library-GSOC

Hi Werner, I was trying to compile FreeType on Windows using Cygwin and I was getting the following error while executing `sh autogen.sh' command even though I have installed the required packages from the Cygwin package installer: -- *Can't locate Automake/Config.pm in @INC (you may need to

Re: Logging Library-GSOC

at 5:17 PM Alexei Podtelezhnikov wrote: > Hi Pryiesh, > > I am sorry I was not following your logging project closely enough. So > I asked the most general question. > > On Tue, Aug 4, 2020 at 7:32 AM Priyesh kumar > wrote: > > > > Hi Alexei, > > Thanks for r

Re: Logging Library-GSOC

PM Alexei Podtelezhnikov wrote: > Hi Priyesh > > On Mon, Aug 3, 2020 at 10:33 AM Priyesh kumar > wrote: > > > > Hi Alexei, > > Is there any update for me regarding Werner's previous mail? > >> > The dlg project contains two configurations: `Debug'

Re: Logging Library-GSOC

Hi Alexei, Is there any update for me regarding Werner's previous mail? Thanks, Priyesh On Fri, Jul 31, 2020 at 11:42 PM Werner LEMBERG wrote: > > > I have added a project under `builds/windows/vc2010/freetype.sln' > > file to build dlg along with FreeType on Windows. > > Thanks. > > > The dlg

Re: Logging Library-GSOC

Hi Werner, I have added a project under `builds/windows/vc2010/freetype.sln' file to build dlg along with FreeType on Windows. The dlg project contains two configurations: `Debug' and `Debug Static' on both `x64' and `Win32' platforms and will be built with FreeType, whenever FreeType is built in

Re: Logging Library-GSOC

Hi, I was working on removing the warnings which get triggered after enabling macro `FT_LOGGING' in ftoption.h file to use dlg library for logging on a file. If `FT_LOGGING' macro is enabled FT_TRACE messages are handled by dlg's API which internally uses a function of `printf' like format,

Re: Logging Library-GSOC

Hi Werner, *> What do your GNU/Linux tests show?* So, I was analyzing time taken by the example program @ here and this time for comparison purpose I have made dlg write logs to stderr. I have used FT2_DEBUG=any:7 with: ./test

Re: Logging Library-GSOC

Hi Werner, *> I suggest the following.* *> (1) Use a different directory (for example> `/submodules/dlg`) for checking out the `dlg`>submodule. This subdirectory won't get distributed with the>FreeType tarball.> (2) Create subdirectory `src/dlg`, which only holds a

Re: Logging Library-GSOC

Hi Werner, As suggested by you I have used `setvbuf()` function in `FT_Message()` function for printing logs on stderr in Full buffering mode when FT_DEBUG_LEVEL_TRACE macro is enabled. For FT2_DEBUG=any:7 and command: main.exe arial.ttf *qwertyuiopasdfghjklzxcvbnm * I have got the following

Re: Logging Library-GSOC

*> This still looks fishy.* Ok, I will try `setvbuf()` function :D *> Probably yes. At least the difference between the two approaches> shouldn't be *that* large, I believe.* *> Well, for comparison purposes the buffering mode should be the same> for `FT_LOGGING` and `FT_DEBUG_LEVEL_TRACE*

Re: Logging Library-GSOC

Hi Werner, *> This looks very unrealistic. Do you redirect data sent to stderr to> an output file?* No, I haven't redirected the data sent to stderr to an output file, for measuring time : ( I thought I have to use the time value which I got when data from stderr is not sent to a .txt file

Re: Logging Library-GSOC

EL_TRACE: linked with FreeType library built with FT_DEBUG_LEVEL_TRACE macro enabled. NO_DEBUGGING: linked with release built of FreeType library Please look into this and provide feedback... Thanks, Priyesh On Thu, Jul 16, 2020 at 11:24 AM Priyesh kumar wrote: > Hi Vincent, > Thanks for t

Re: Logging Library-GSOC

Hi Vincent, Thanks for the suggestion it seems very helpful, I will try it and let you know in case of any query. Thanks, Priyesh On Thu, Jul 16, 2020 at 4:14 PM Vincent Torri wrote: > On Thu, Jul 16, 2020 at 9:51 AM Werner LEMBERG wrote: > > > > > > >> *Have you set `FT2_DEBUG=any:7` in the

Re: Logging Library-GSOC

> *Have you set `FT2_DEBUG=any:7` in the environment?* Sorry, I forgot to mention this, I have used FT2_DEBUG=any:7 with OpenSans-Bold.ttf font. *> You should also use a> well-hinted TrueType font like 'Arial' to get a large bunch of> instruction debugging.* Thanks, I will use this font.

Re: Logging Library-GSOC

ugging using FT_LOGGING mode (avg time: 0.0512144) Please look into this and provide feedback... Thanks, Priyesh On Tue, Jul 14, 2020 at 4:43 PM Priyesh kumar wrote: > Hi again, > I accidentally sent the previous mail > Continuing to the previous mail... > Also in the requirements

Re: Logging Library-GSOC

with MakeFile, therefore could you provide me some references from where I can read about doing this... Thanks, Priyesh On Tue, Jul 14, 2020 at 4:37 PM Priyesh kumar wrote: > Hi, > I have added an option in `FT2_DEBUG` environment variable to > enable/disable the > printing of FT_COMPONENT a

Re: Logging Library-GSOC

to provide an option in MakeFile `make dist On Sun, Jul 12, 2020 at 2:50 PM Priyesh kumar wrote: > Hi armin, > > *> This would print wrong-ish timestamps that couldn't really be used for > profiling (I mean, it could; you just have to know which timestamp belongs > to which message)

Re: Logging Library-GSOC

Hi armin, *> This would print wrong-ish timestamps that couldn't really be used for profiling (I mean, it could; you just have to know which timestamp belongs to which message). I would suggest to * *> rather store a flag after reading `\n` and attach the timestamp to the following message.* I

Re: Logging Library-GSOC

*> I thought of> [] ...> where is the value given in the `FT_COMPONENT` macro,> padded with spaces to ensure a uniform width. Example:> [cffdriver] ...> [psconv ] ...> [sfobjs ] ...> However, this should be freely adjustable – thus my request to make> `{` and `}` configurable in the

Re: Logging Library-GSOC

*> Oh yes, you can! Either you modify the source code of 'dlg' within> FreeType, or – which is better IMHO – you submit a feature request or> patch to the 'dlg' maintainers that allows control of the '{' and '}'> characters for marking tags. I see no reason why this must be> hard-coded.* Ok, I

Re: Logging Library-GSOC

*> Of course. Please send a separate patch for these fixed so that I can> apply it to master directly.* Ok, I will provide you the patch once done... *> Very nice! Do you have some data how large the slowdown is due to the> additional code?* No, As I haven't done software profiling before

Re: Logging Library-GSOC

> *Since debugging isn't time critical it might be necessary to add an> additional step that scans tracing messages for newline characters,> then massaging the output by inserting the time stamp. In other> words, all occurrences of> `\n`> should be replaced with> `\n[time stamp] `> or

Re: Logging Library-GSOC

Hi, I have updated the progress report for this week @ here It contains a brief description of all the useful APIs provided by dlg Please look at the report... Thanks, Priyesh On Thu, Jun 25, 2020

Re: Logging Library-GSOC

Hi Werner, *> Well, you say 'most'. Is this, say, 70% or 90% suitability in your> opinion? If it's the former, how much additional code must be added> to fit the needs? There might be a point that you have to add so much> code that it might be easier to avoid the library altogether.*

Re: Logging Library-GSOC

Hi Werner, > *Thanks! The recent discussion with Behdad reminded me to ask you> whether you have also investigated the case where you modify the> existing debugging and tracing code of FreeType without using an> external library. For example, such new code might be based on the> code from

Re: Logging Library-GSOC

Hi Guys, > *I do like that notation style ;) Apart from that I for sure have not used it on Windows; don't worry about that either and thanks for double-checking! :)* Thanks for responding to my concerns... >* As you are now moving into the implementation phase of your project I would quickly

Re: Logging Library-GSOC

Hi, > *OK, then let's try this library!* Thanks for the reply, will work in this direction... Thanks, Priyesh On Fri, Jun 19, 2020 at 9:44 AM Werner LEMBERG wrote: > > > During the exploration phase, I have seen several libraries and > > according to me *dlg* is best suited for the

Re: Logging Library-GSOC

On Wed, Jun 17, 2020 at 2:18 PM Priyesh kumar wrote: > Hi Werner, > > *I think you did a great job with your exploration.* > > Thanks... > > > *Do you think that** you already can suggest a library that fits best?* > > I think I need some time to analyze the alre

Re: Logging Library-GSOC

Hi Werner, > *I think you did a great job with your exploration.* Thanks... > *Do you think that** you already can suggest a library that fits best?* I think I need some time to analyze the already explored logging libraries (mainly dlg and log4c) w.r.t to FreeType, and how to leverage these

Re: Logging Library-GSOC

as you have worked with log4c before... Thanks } After going through log4c, I don't think I have any more options to look onto... If you guys know any more logging libraries, please let me know... Thanks, Priyesh On Mon, Jun 15, 2020 at 10:47 AM Priyesh kumar wrote: > Hi Armin, > >

Re: Logging Library-GSOC

Hi Armin, *>However, I could see how e.g. the usage of `FT_COMPONENT` could be slightly altered (or an additional macro introduced) if that helps with moving more functionality into the logger.* Please, could you provide more information on this... Thanks, Priyesh On Sun, Jun 14, 2020 at 3:24

Re: Logging Library-GSOC

Hi armin, >*Thanks for your update & write-up, looks promising :) I agree with your approach of trying to find the most lightweight C logger that does the job* Thanks for reviewing the report... Regarding Qus 1) *>do you plan to mainly using the logger to write to files and an equivalent of

Re: Logging Library-GSOC

Hi Werner, I have updated the progress report for this week @ here Thanks, Priyesh On Sat, Jun 6, 2020 at 8:34 PM Werner LEMBERG wrote: > > > The gnulib repository provides a module 'unistd' for

Re: Logging Library-GSOC

Hi Werner, >*What is your favourite logging library right now?* I am currently looking at a library called EasyLogger ( Github Link: https://github.com/armink/EasyLogger ). I would say it could be my favourite logging library as it satisfies most of the requirements. But the problem is that the

Re: Logging Library-GSOC

Hey, This week I have explored several libraries and I have prepared a report mentioning their pros and cons @here I am using Visual Studios 2019 to build libraries on windows, and while exploring

Re: Logging Library-GSOC

Hey guys, After going through the discussion, I think I am confused about the actual requirements from the project. Clearly there is some problem with the current logger, but I think the requirements which are mentioned on the FreeType's GSoC page and the requirements which are discussed being

Re: Logging Library-GSOC

Thanks for the reply, *>Basically yes. As an improvement, I would like that the value of the>`FT_COMPONENT` macro can be displayed optionally, e.g.>[afhints] foo bar>[ttgxvar] sproink>...>The idea is that you first do a run with `FT2_DEBUG=any:7:labels` to>see all those tags, then

Re: Logging Library-GSOC

anges according to the external library... Thanks, Priyesh On Mon, May 18, 2020 at 3:46 PM David Turner wrote: > > > Le lun. 18 mai 2020 à 10:49, Priyesh kumar a > écrit : > >> Thanks for the reply... >> >> *>I recommend not baking details of the logging library into t

Re: Logging Library-GSOC

Thanks for the reply... *>I recommend not baking details of the logging library into the rest of FreeType whenever possible. One thing that can be done is to send structured logs from FreeType, i.e. instead of >FT_Message() sending a string to whatever log, the function could instead send a

Re: Logging Library-GSOC

Hey, I wanted to ask that after selecting desirable external library how should I proceed: 1. Should I stick to the existing debugging facility in which filtering of log messages is based on debug level comparisons of various FreeType's components and only use the external library to write log

Logging Library-GSOC

Hey, I was exploring the logging libraries as per the requirements, and I was thinking of adding functionality to automatically check whether the logging library is installed or not as FreeType does for other libraries like Harfbuzz and libpng. But most of the logging libraries which I have seen

Requirements from external logging library

Hello everyone, As according to my GSOC project which is integrating an external logging library with FreeType. I need some help gathering the requirements that the external library should satisfy. >From earlier discussion, below are basic some requirements: 1. It should be written in C language

GSOC

Hey, I am glad to know that I got selected for the GSOC. I would like to thank my mentor @Werner LEMBERG and all other community members for their continuous support and guidance. I am very excited to work in FreeType and will need further guidance and support from this group. Thanks again!!

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

Re: tracing and logging library - GSOC Project

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 inve

Re: tracing and logging library - GSOC Project

*>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,

Re: tracing and logging library - GSOC Project

direction.. On Thu, Feb 27, 2020 at 10:14 AM Priyesh kumar wrote: > > > > *>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 feat

Re: tracing and logging library - GSOC Project

*>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.

tracing and logging library - GSOC Project

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