On Mon, 22 Mar 2010, Szak�ts Viktor wrote:

Hi Viktor,

> > Can you describe what are the exact problem with
> > current directory structure?
> > It allows to keep SQLRDD code in one directory tree
> > what seems to be clean solution for me better then
> > dividing it into few directories in contrib dir.
> I have to maintain rddsql specific hacks in 
> postinst.prg and packaging in winuni dir.
> 'Maintain' means: Do it manually, develop script 
> for it, test it, all this just for the sake of 
> this exception. I especially don't like to 
> hard-wire contrib names in any non-contrib parts 
> of Harbour, but this is currently impossible.
> Current solution also requires special chaining 
> of .hbc files, which makes them impossible to 
> move like the other .hbc files, it also requires 
> special logic for rddsql header inclusion as 
> opposed to standard HB_INC_DEPEND method. I could 
> go on.

As I can see postinst.prg creates hbmk.cfg file which
contains the following lines:

   libpaths=../contrib/%{hb_name}
   libpaths=../contrib/rddsql/%{hb_name}
   libpaths=../addons/%{hb_name}
   libpaths=../examples/%{hb_name}

so I guess you want to remove the second one.
But can you explain what above lines does?
I was always wondering why I have it in hbmk.cfg
when I do not have any of above directories in
my Harbour installation.

rddsql string is also used inside
package/winuni/mpkg_win_uni_extra_copy.bat
It's used to copy 'test' subdirectories and *.hbc files
to some F:\hb\hb20\. I do not know what this code does
and why it uses hardcoded F:\hb\hb20\. I only guess
that it's bound in some way with generated hbmk.cfg.

Maybe if you explain what hbmk.cfg does and why it
uses such hardcoded directory structure then I will
understand what you are trying to do. It should help
all of us in adding new directories to SVN code.
Now seems that we have some undocumented conditions
which we should respect.

best regards,
Przemek
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to