Built some new Packages for Slackware...
I have built some new stuff for Slackware 13...
This is Engineer's stuff, so, pls forgive me for not giving that much attention to other kinds of apps, that may be more the like of the reader ... :)
I Have built :
Should anybody be interested in any of this, I will gladly share how I did it.
Why don't these guys at Simulia, Dassault Systemes, Autodesk, etc free their source code for us slackers to build Abaqus, Catia, and Inventor for Slackware... ?? :)
PS: Given that CGX, CCX, XFoil and AVL are number-crunching CPU hogs, I used Intel compilers to build them, but the results can easily extrapolate to gcc/gfortran.
You could submit your slackbuilds to www.slackbuilds.org to share with the community.
Yup that'd be better! Most slackers rely on Slackbuilds.org for their packages! Good work btw! :)
Hi @tramni1980 @Shylock
I would really like to make Slackbuilds for these.. but I guess that I am not competent enough... :
for all the packages that I built, there was an extensive hackery... ( only exception made to cgx , ( a standard ./configure make trackinstall ) :
I had to create parallel 3 source trees, hack into the makefiles of 2 of them in order for them to build double precision libraries with ifort from INTEL, hack into one source file of the spooles library, to fix an illegal unreferenced function definition ( this is "set" to build in Fotran Compiler of Cray systems ), cd into the main source tree, and finally type make, not before having also hacked the makefile so that the fortran Linker of Intel would not try to find some _MAIN ( -nofor-main directive ) anmd use C++ linker instead.
All this about cgx... AVL and XFoil are only "a bit" harder... but still manageable...
Wings 3d will go easily, once you install ERLANG OTP from slackbuilds, and ESDL library ( erlang bindings for sdl )...
... wether it will run smoothly without segfaulting, this is another story... sometimes it does... sometimes it does not....
Has a will of its own .... :)
So... for me to automate all this in a slackbuild... it would require me to master sed, and awk.... I am working on this... but I am still "grasshoper".... :D
Although the Slackware philosophy encourages the smallest amount of patching as possible, there are times when it's unavoidable, and it seems to me to be the most transparent way of making changes to a source tree.
As far as the "Why don't..." question: well the usual answer is Money, in one form or anoher.
|All times are GMT -5. The time now is 09:02 PM.|