Tiny Core Base > CorePlus
Installation of aircrack-ng,hashcat,hcxdumptool,hcxpcaptools,reaver
Sashank999:
Thanks @Rich for the web site. Now, with a wiki, I can use TCL a bit more.
@Juanito
Not for personal extensions. I wanna make extensions for all x86 TCL users.
I like to compile more tools and upload them to the repo of TCL so that other TCL users may not face the trouble of compiling.
Rich:
Hi Sashank999
--- Quote from: Sashank999 on June 03, 2020, 02:36:43 AM --- ... @Juanito
Not for personal extensions. I wanna make extensions for all x86 TCL users. ...
--- End quote ---
The instructions that Juanito provided should work for all packages using make, both personal and otherwise.
Besides the Wiki, maybe this writeup will be of some use:
http://forum.tinycorelinux.net/index.php/topic,23844.msg149748.html#msg149748
There is also a build script attached that you can use to see all (I hope) of the steps involved.
Sashank999:
Thank You @Rich . The script looks amazing. It automates all things without human interactions. I will try to create one.
At present, I made .tcz files with mksquashfs for hcxdumptool,hcxtools, aircrack-ng. But I don't know the license things. Once I know about it, I will separate all libs, manpages, executables, create .info, .md5, .dep and mail it.
Any tips about what to do with the licenses for hcxtools, hcxdumptool, aircrack-ng ?
Sashank999:
aircrack-ng has GPL v2 and both hcxdumptool and hcxtools have MIT license.
And also, should I follow the flags mentioned in your script for my x86 TCL ?
In your script, x86 flags are in case i686 and I am assuming they are the flags for all x86 TCL PCs.
CFLAGS=" -flto -march=i486 -mtune=i686 $OPTIMIZE -pipe -fno-plt"
# CXXFLAGS="g++ -flto -march=i486 -mtune=i686 $OPTIMIZE -pipe -fno-plt -fno-exceptions -fno-rtti"
LDFLAGS="-Wl,-T/usr/local/lib/ldscripts/elf_i386.xbn"
aus9:
Until you get a better reply
--- Quote ---Any tips about what to do with the licenses for hcxtools, hcxdumptool, aircrack-ng ?
--- End quote ---
I did post a wiki link at reply 16 on how to create a TCE, you must have missed it. ;D
You may like to read "Required Files"
those licences, GPL or MIT may not specifically require accompanying with the exe.
but you mention a man page.
If any look like they do need accompany major portions of your software then the gurus use
/usr/local/share/doc/TCE-name/<some-licence> as the preferred dir for it to unpack to.
You can see example of both man page and some docs here
http://tinycorelinux.net/11.x/x86_64/tcz/gutenprint-doc.tcz.list
on 64 bit the man viewer is supplied by man-db.tcz but it looks like it might be supplied by
man.tcz on 32 bit.
try loading it and your TCE-doc and running
--- Code: ---man <some-name>
--- End code ---
to see if a man page appears.
If that works, consider making man.tcz a dep of your doc TCE.
otherwise specify it in your comments to doc please.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version