I am trying to make a library now. However, some clues about expected params to
ar probably is necessary. I have some to chose from:
Code: Select all
bash-3.2$ ar --man
usage: ar -d [-TLsv] archive file ...
ar -m [-TLsv] archive file ...
ar -m [-abiTLsv] position archive file ...
ar -p [-TLsv] archive [file ...]
ar -q [-cTLsv] archive file ...
ar -r [-cuTLsv] archive file ...
ar -r [-abciuTLsv] position archive file ...
ar -t [-TLsv] archive [file ...]
ar -x [-ouTLsv] archive [file ...]
I expect that I need to run
ar (or
xmosar instead?) in Terminal.
xmosar --help
Code: Select all
bash-3.2$ xmosar --help
Usage: xmosar [emulation options] [-]{dmpqrstx}[abcDfilMNoPsSTuvV] [member-name] [count] archive-file file...
xmosar -M [<mri-script]
commands:
d - delete file(s) from the archive
m[ab] - move file(s) in the archive
p - print file(s) found in the archive
q[f] - quick append file(s) to the archive
r[ab][f][u] - replace existing or insert new file(s) into the archive
s - act as ranlib
t - display contents of archive
x[o] - extract file(s) from the archive
command specific modifiers:
[a] - put file(s) after [member-name]
[b] - put file(s) before [member-name] (same as [i])
[D] - use zero for timestamps and uids/gids
[U] - use actual timestamps and uids/gids (default)
[N] - use instance [count] of name
[f] - truncate inserted file names
[P] - use full path names when matching
[o] - preserve original dates
[u] - only replace files that are newer than current archive contents
generic modifiers:
[c] - do not warn if the library had to be created
[s] - create an archive index (cf. ranlib)
[S] - do not build a symbol table
[T] - make a thin archive
[v] - be verbose
[V] - display the version number
@<file> - read options from <file>
--target=BFDNAME - specify the target object format as BFDNAME
emulation options:
No emulation specific options
xmosar: supported targets: elf32-i386 a.out-i386-linux pei-i386 elf64-x86-64 elf32-x86-64 pei-x86-64 elf64-l1om elf64-k1om elf64-little elf64-big elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex
Report bugs to <http://www.sourceware.org/bugzilla/>
I assume that while I develop the library I only work within xTIMEcomposer and then I won't need
xmosar (not
ar, really?) before I am going to export the code?
I am trying to log my work
here (standard disclaimer: no money, ads, gifts; only fun and expenses).
Off Topic
Bear in mind that this is the first time ever I would make a library and I am sitting alone. At work with lots of embedded controllers we just reused the code base, that branched off. A library comes at a price (like do I really want to make it that general. I listened to a lecture once by a guy at (then) Philips. He said it (then) cost 5-10 times more to make a library, when the source was being used in a variety of products)