If this works well, we may not need to make them in postinst
phase. We'd still need however the link creation logic at
postinst, but that's sh specific anyway.

I tried it. Just a few notes after testing some builds.
1. in native Linux build 'lib' prefix is missing in library name

Easy to solve.

2. shared libraries do not contain GTCRS and GTSLN

Probably also. I'll have to check.

3. they are not linked with system libraries

Could you fix this. I have no idea what's this all about still.

4. in Linux builds shared libraries are not created for suncc and icc

I didn't add support until I knew the issue with Linux ones.
If that's alright, it's pretty much copy/paste.

5. in mingw cross builds harbour-20.a and harbourmt-20.a without lib
  prefix are created. Additionally they are not necessary for mingw
  because it can create import library for harbour*.dll online.
  The same problem is with MinGWCE builds.

I'll check. I opted to create implibs for mingw also. I know it's
not necessary. We can probably delete them if that's an issue.

6. bcc builds fails when sh shell is used due to forward slashes
  instead of backslashes in file names

Yeah. Noticed it, however I tested under msys, and it broke
in a very strange way. If you can pls fix it in bcc.mk.

7. I do not see any easy way to include some other libraries
  in custom builds, i.e. for my won use I used to create shared
  libraries with some contrib ones like hbct and some of my own
  like dbrmap.

Generally I find this a very bad idea. IMO harbour dll should
provide some well described set of functionality, otherwise
they aren't replacable / etctec. Instead we should rather think
about adding dll support for each contrib individually. I didn't
think about this yet though, since this is very new topic.

Anyhow with hb-mkdyn.sh such customized dynlibs can be created,
but that doesn't seem to be the job of our GNU Make system IMO.

Brgds,
Viktor

_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to