Re: SPIRO_SELECT etc

2018-03-30 7:20 GMT+03:00 Jose Da Silva <[email protected]>:

>
> Some linux distributions have two types of files to download,
>  - a binary file (uses less disk space on the computer)
>  - a developer version (has extra files needed to build something).
>

Some people do not use Linux for their own reasons. I am one of them.

> Since you are not installing a prebuilt binary, but have decided to build
> your own, you will also need developer versions of libraries used.
>

Since I compile and use FontForge for about 15 years I know this...
And so I have compiled and installed linbspiro as I wrote in my message.


> The developer version includes header *.h files expected to be used during
> the building steps of fontforge.
>

Unfortunately, the header files do mot contain these declarations.
Googling for the
missing symbols I found the following page

https://www.apt-browse.org/browse/ubuntu/trusty/main/i386/libfontforge-dev/20120731.b-5/file/usr/include/fontforge/splinefont.h

As you can see these declaration are part of FontForge not part of libspiro.


> Reading the messages above, you need to install the developer version of
> libspiro first.

Let's follow your advise:

$ git clone https://github.com/fontforge/libspiro.git
Cloning into 'libspiro'...
remote: Counting objects: 548, done.
remote: Total 548 (delta 0), reused 0 (delta 0), pack-reused 548
Receiving objects: 100% (548/548), 772.82 KiB | 480.00 KiB/s, done.
Resolving deltas: 100% (307/307), done.
Checking connectivity... done.
$ cd libspiro/
$ grep SPIRO_SELECT *
grep: java: Is a directory
grep: m4: Is a directory
grep: tests: Is a directory
$ grep -R SPIRO_SELECT *
$

As you can see no sign of SPIRO_SELECT!

>
> When you bootstrap, you need to pay attention to the text output.
> Some of the messages are warnings, others are errors, but still allow you
> to keep going. If there are error or warning messages mentioned during
> bootstrap, you will probably want to answer those first.
> When all errors and warnings are answered in ./bootstrap, then the should
> see a ./configure that needs to be run. After running ./configure you will
> then have Makefile.in and also (more importantly) a Makefile
>

I can have the Makefile only if I have a template which was clearly missing.
Since there is no template, configure cannot create a Makefile, I have
compiled zillions of things and I think I know a thing or two.

Have a nice day!

A.S.
-- 
Apostolos Syropoulos
Xanthi, GREECE

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html