Blackfin and version scripts

Werner Koch wk at
Wed Jun 23 09:46:01 CEST 2010

On Wed, 23 Jun 2010 07:29, rra at said:

> I can take a pass at starting.  All that I need for my packages is to
> support the basic version syntax:
>     <version> {
>       global:
>         <symbol>;

That would be sufficient for me too as long as a <version_2> with only
global symbols is supported as well.

Having a second file with a simple list of symbols instead of a version
script parser is another option.  Actually this is required because to
support W32 we need a .def file

      gcry_check_version  @1
      gcry_control  @2

which allows to assign id numbers to symbols.  In theory we could add
this via comment lines to a versions script but that would make a parser
even more complicated.  In some projects I create the .def file from a file to handle differences between W32 and W32CE.  In any case
the .def file is easy to parse and could be used as input to



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

More information about the Gcrypt-devel mailing list