|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | 03-May-2022 | - |
| obj/ | H | 03-May-2022 | - | 2 | 2 |
| FAQ | H A D | 26-Oct-2015 | 2.3 KiB | 74 | 57 |
| Makefile | H A D | 27-Oct-2015 | 7.3 KiB | 239 | 171 |
| README | H A D | 16-Nov-2014 | 2.3 KiB | 64 | 56 |
README
1If you want to override /usr/local as the default prefix
2(which means /usr/local/include would have the header file and
3/usr/local/lib would have the library files), then run
4make, make install and make uninstall (to build, to
5install and uninstall respectively - you need it for
6all three as I explain below) :
7
8make PREFIX=/tmp
9make PREFIX=/tmp install
10make PREFIX=/tmp uninstall
11
12The last two will of course have to be done
13as root if you need permissions to write to
14the directory (for /tmp you wouldn't unless
15the files already existed by someone else and
16you didn't have permission).
17
18In any case, the above would install header file
19under '/tmp/include' and the library file(s) under
20'/tmp/lib'.
21
22If you want to know the technical details as to why
23you have to (when overriding the install location)
24specify PREFIX= even when building, see the FAQ
25file (summary: it makes it easier for you when linking
26in the shared library).
27
28A word of caution to those overriding prefix :
29--
30You are more than welcome to disregard this but I feel
31it is something I should bring up. If you do override
32the prefix I strongly recommend you do not specify
33'/usr'. Why one might ask. The typical way is
34that user-compiled programs/libraries/etc. go under
35'/usr/local' (other times '/opt'). This has multiple
36benefits: you keep '/usr' clean and if you have a
37package manager then it makes it easy to say:
38"The only files under /usr/include and /usr/lib are
39those that belong to a package."
40In other words it is easier to maintain integrity
41and verify everything. Most important of it all
42(aside the security implications) is this:
43You have less chance of name clashes. If there ever
44is a package that installs to /usr and it includes
45the files (maybe a package for AngelScript) then you
46will have issues.
47--
48
49Lastly: I don't have a way to test the phone builds
50so I cannot verify the build process (it really
51depends on the environment and architecture, like
52most things); I'm an old-timer that hates the
53"smart" trend (besides: it is a horrible misuse
54of the world 'smart').
55
56CONTACT:
57If you have any questions or concerns, by all
58means have Andreas contact me (at this time I
59don't have an email I feel okay sharing - if it
60seems this is of use to others I will likely
61create an email on my server for this very
62purpose). For now Andreas can forward the
63message to me.
64