CharLs-2.0.0 slack build script help....
 

I would like to submit this file in the SBo but first I need to make a slack.build script can someone help me.



mkdir build
cd build
cmake .. \
-DCMAKE_C_FLAGS_RELEASE:STRING="-DNDEBUG" \
-DCMAKE_CXX_FLAGS_RELEASE:STRING="-DNDEBUG" \
-DCMAKE_Fortran_FLAGS_RELEASE:STRING="-DNDEBUG" \
-DCMAKE_INSTALL_PREFIX:PATH=/usr \
-DSYSCONF_INSTALL_DIR:PATH=/etc \
-DINCLUDE_INSTALL_DIR:PATH=/usr/include \
-DCMAKE_INSTALL_LIBDIR:PATH=/usr/lib${LIBDIRSUFFIX} \
-DLIB_INSTALL_DIR:PATH=/usr/lib${LIBDIRSUFFIX} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DSHARE_INSTALL_PREFIX:PATH=/usr/share \
-DMAN_INSTALL_DIR:PATH=/usr/man \
-DCMAKE_BUILD_TYPE:STRING=Release \
-DBUILD_SHARED_LIBS:BOOL=ON \
-DCMAKE_SKIP_RPATH:BOOL=ON \
-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \
-DBUILD_SHARED_LIBS:BOOL=ON \
-Dcharls_BUILD_SHARED_LIBS:BOOL=ON\
-DCMAKE_VERBOSE_MAKEFILE=ON\
-DBUILD_TESTING=ON \
|| exit $?

make

Here are the commands that need to be in this script
http://www.geocities.ws/reddoglinux/CharLS-2.0.0.tar.gz
and here is the tar file in question.

What you would want to do in this situation is use a www.slackbuilds.org template and change it to the specifics of your package. For your project you will need the cmake template

https://www.slackbuilds.org/templates/

then follow the slackbuilds submission guidelines here
https://www.slackbuilds.org/guidelines/

As a courtesy I made a SlackBuild of charls-2.3.4. Take it and do what you want with it, if you plan on submitting it to SBo you will need to make the info file and README to make it compliant to submit to SBo.

https://www.dropbox.com/s/ywfk2wgo6a...ls.tar.gz?dl=1

Thank you for pointing me in the right direction I am working on aeskulap -0.2.2beta2 and dcmtk-3.6.6 to submit them for slackbuild I just need the right direction and Daedra you point me there again I thank you.

Ok Daedra can you verify that these source code and builds work on you computer??
Dependencies are CharLS-2.3.4, libglademm-2.6.7, & gconfmm-2.28.3
I worked on these 3 packages to build cause my wife is a Medical Assistant and she needed a DICOM Viewer like she has on her Linux Mint System.

http://www.geocities.ws/reddoglinux/aeskulap-0.2.2.txz
http://www.geocities.ws/reddoglinux/...2-x86_64-4.txz
http://www.geocities.ws/reddoglinux/dcmtk-3.6.6.txz
http://www.geocities.ws/reddoglinux/...6-x86_64-4.txz

What order should I install them or does it matter?

Um I had to install these first libglademm-2.6.7, & gconfmm-2.28.3
then CharLS, dcmtk and last was asekulap
For some reason i had to reboot my computer though after installation.
I think I'm missing a command in the doinst.sh file so that everything can run with out rebooting.

Ok giving it a go right now. I will report back shortly.

Thank you so much.

Ok after installing the required dependencies from SBo, and charls from the slackbuild I posted above I moved on to dcmtk. It finished successfully but there is an error in the finished package. The /usr/share/ path is incorrect, it is installing to /usrshare. See the attached output.

Should be an easy fix. I will look at the Slackbuild. It is getting late here and I have to work tomorrow so I may not get any more done tonight, but I will test again tomorrow.

ok I see it, change

to

Yep I ran into that as i was testing I fixed the build script I am waiting to for the recompile to be done.

I will repost current links and thank you so much for all your help I'm going to keep these build scripts and continue on in my Journey.... :)

ok just corrected dcmtk and rebuilt and installed. Then did aeskulup and it built and installed fine. The hard part is done, you got working slackbuilds. Going to go to bed, but what I did see is that the files still need the .info file and the README to be compliant for SBo submission. And aeskulup needs a doinst.sh file with the following...

I checked dcmtk-3.6.6 and it errored out like it could not find /usr//usr/share/dicom.dic so I am recompiling it one last time and omitting -DCMAKE_INSTALL_DATADIR:PATH=/usr/share \ with -DCMAKE_INSTALL_DATADIR:PATH=share \ to see if the file is found correctly.