Hello Radek, On 3/3/21 17:40, Radosław Korzeniewski wrote: > Hello, > > The readline manual (from Debian) gives: > > READLINE(3) > > Library Functions Manual > > READLINE(3) > > NAME > readline - get a line from a user with editing > > SYNOPSIS > #include <stdio.h> > #include <readline/readline.h> > #include <readline/history.h> > > So, I assume that a correct way to include readline headers is as above. > But is this Linux specific?
Yes, this is specific and probably some version of linux only (recent ones, but probably not old ones, or the one installed manually). > I'm asking as Bacula uses: > > #include "readline.h" > #include "history.h" > > which in my understanding is incorrect. This is not incorrect, everything depends on the ./configure detection, it includes the different path to the readline via something like CFLAGS or an other Makefile variable. Changing these two lines requires to update the configure and test on many platforms. Did you see a problem while compiling ? > What do you think? If all systems are using it, it's ok, but I believe that it's not the case. Systems where the readline is directly inside include/ will not compile with <readline/readline.h> while they can compile with the current code. Some people might call that a regression :-) Best Regards, Eric _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
