SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In file included from frame.cpp:21:
frame.h:32:18: error: CImg.h: No such file or directory
In file included from frame.cpp:21:
frame.h:34: error: 'cimg_library' is not a namespace-name
frame.h:34: error: expected namespace-name before ';' token
frame.h:75: error: ISO C++ forbids declaration of 'CImg' with no type
frame.h:75: error: expected ';' before '<' token
frame.h:76: error: 'CImg' has not been declared
frame.h:76: error: expected ',' or '...' before '<' token
frame.cpp: In member function 'void Frame::applyFilters()':
frame.cpp:446: error: 'CImg' was not declared in this scope
frame.cpp:446: error: expected primary-expression before 'unsigned'
frame.cpp:446: error: expected ';' before 'unsigned'
frame.cpp:461: error: 'image' was not declared in this scope
frame.cpp:462: error: expected type-specifier before 'CImg'
frame.cpp:462: error: expected ';' before 'CImg'
frame.cpp:463: error: 'image' was not declared in this scope
frame.cpp:466: error: 'image' was not declared in this scope
frame.cpp:467: error: expected type-specifier before 'CImg'
frame.cpp:467: error: expected ';' before 'CImg'
frame.cpp:468: error: 'image' was not declared in this scope
frame.cpp:471: error: 'image' was not declared in this scope
frame.cpp:472: error: expected type-specifier before 'CImg'
frame.cpp:472: error: expected ';' before 'CImg'
frame.cpp:473: error: 'image' was not declared in this scope
frame.cpp:476: error: 'image' was not declared in this scope
frame.cpp:477: error: expected type-specifier before 'CImg'
frame.cpp:477: error: expected ';' before 'CImg'
frame.cpp:478: error: 'image' was not declared in this scope
frame.cpp:483: error: 'image' was not declared in this scope
frame.cpp:484: error: expected type-specifier before 'CImg'
frame.cpp:484: error: expected ';' before 'CImg'
frame.cpp:494: error: 'image' was not declared in this scope
frame.cpp:496: error: 'image' was not declared in this scope
frame.cpp:498: error: type '<type error>' argument given to 'delete', expected pointer
frame.cpp: At global scope:
frame.cpp:550: error: expected constructor, destructor, or type conversion before '<' token
make[2]: *** [frame.o] Error 1
make[2]: Leaving directory `/tmp/SBo/wxcam-1.0.4/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/SBo/wxcam-1.0.4'
make: *** [all] Error 2
http://slackbuilds.org/, it's basically a user repository for Slackware packages - still without dependency checking. You use sbopkg through the cli as root to acces sbo.
First sync it, then search for wxcam, add it to the queue, and then read the README to see what the dependencies are. Add those to the queue - but make sure you check their dependencies, and then make sure it's all in order - wxcam being on the bottom or final position. Then process the queue.
Oh well, I give up. 4 hours trying to get a webcam program is ridiculous. As much as I despise Windows, I never have to waste time like this. This is exactly why I gave up on linux years ago, and it looks like they haven't made much progress in this area.
One dependency depends on another then another and then another, but wait 2.0 won't work you need 2.0.1. Now that you have all the dependencies, you get 100 compile errors for whatever reason. Oh look, it is in /usr/local/ not /usr/var and won't compile as it's the wrong path - and it just goes on and on and on. Don't know how you guys deal with this crap, it drives me insane.
configure: error: *** GTK not found *** It's there, so I am assuming wrong path as above or maybe wrong version.
My apologies for the ranting, but this is why I gave up on Linux before. I thought by now this type of thing would have been changed, not to mention all the other problems I have encountered in the last 4 days since installing Slackware.
Thanks to everyone for the help, guess I'll check in another couple years to see if Slack is ready for mainstream use yet, at which point my webcam will probably be out of date again and I'll have to buy another new one. LOL
Perhaps a binary-based dependency-resolving distribution would be more suitable for you if you cannot deal with compiling software. Ubuntu, Debian, Mint, Fedora, OpenSUSE, the list goes on. Considering Slackware is fairly unique amongst Linux distributions (especially when it comes to its philosophies), putting down the entire Linux community because you are unhappy with Slackware is probably less than appropriate (or accurate).
Thanks to everyone for the help, guess I'll check in another couple years to see if Slack is ready for mainstream use yet, at which point my webcam will probably be out of date again and I'll have to buy another new one. LOL
Funny. My QuickCam Express works out of the box as well as my QuickCam 3000 Pro.
I was just looking at another post in this group profiling some other distros and may just do that, but my question to the developers is this, how hard can it be to do one of the following.
Have a dependency check that will offer to download and install any needed dependencies (this is the one I would do).
Include what is needed in the package you are installing, if already installed on your system it will bypass it.
Give you a detailed list of the programs and versions that are needed.
Or something else.
As a programmer myself, I know the first one is possible and would defanately make things easier.
Thanks again to all that responded, except for Richard Cranium.
I can't help but think your making a mistake installing wxCam. Installing '50' dependencies shouldn't be required. The Slackbuild lists 4 dependencies, each of which do not have any additional dependencies.
All that should be required is installing these 4 required slackbuilds packages first and then installing the slackbuild for wxcam.
While it sounds like your fed up with the lack of dependency handling, maybe you should look into something like Ubuntu. Saying things like 'slackware isn't ready for mainstream use' isn't exactly fair.
This is starting to go off-topic, but Slackware isn't, and never will be, ready for mainstream, and I don't want it to be mainstream. In order to go mainstream it would have to abandon its philosophies, which constitute why I use Slackware in the first place. Beauford2008, many, MANY (the vast majority) of distributions, both binary- and source-based, do as you ask. Slackware doesn't by design. If dependency resolution is what you're after, you would likely be much happier using something else. To call it a flaw of Slackware, however, ignores the philosophies behind Slackware and the reasons for its continued existence -- just because you are unhappy with it doesn't necessarily mean everyone else is. Try other distros with philosophies more inline with your own and I'm sure you'll be much happier.
I can't help but think your making a mistake installing wxCam. Installing '50' dependencies shouldn't be required. The Slackbuild lists 4 dependencies, each of which do not have any additional dependencies.
All that should be required is installing these 4 required slackbuilds packages first and then installing the slackbuild for wxcam.
While it sounds like your fed up with the lack of dependency handling, maybe you should look into something like Ubuntu. Saying things like 'slackware isn't ready for mainstream use' isn't exactly fair.
Regards
This is what makes it even more frustrating when you follow the instructions to the letter and it still doesn't work, and it is the package that is screwing up. I just type installpkg whatever.tgz so if it doesn't work or gives me an error, then what? As I said in an earlier post, it is looking for GTK which is for sure installed, so why does it think it is not?
Well the dependencies and wxCam are busy compiling away on my own 13.1 system just to check. My webcam (inbuilt eeePC camera) has worked on online chat sites (meebo etc). I'll report back any issues.
Edit:
Compilation just finished without a hitch. Started wxCam and it picked up my hardware instantly with no problems.
How exactly are you installing these packages?
Usual process goes a little somthing like:
- download source tarball and slackbuild tarball
- extract slackbuild tarball
- mv source tarball into resulting directory
- cd to this directory
- sudo sh XYZ.Slackbuild
- wait patiently
- cd /tmp
- sudo installpkg XYZ.tgz
This is starting to go off-topic, but Slackware isn't, and never will be, ready for mainstream, and I don't want it to be mainstream. In order to go mainstream it would have to abandon its philosophies, which constitute why I use Slackware in the first place. Beauford2008, many, MANY (the vast majority) of distributions, both binary- and source-based, do as you ask. Slackware doesn't by design. If dependency resolution is what you're after, you would likely be much happier using something else. To call it a flaw of Slackware, however, ignores the philosophies behind Slackware and the reasons for its continued existence -- just because you are unhappy with it doesn't necessarily mean everyone else is. Try other distros with philosophies more inline with your own and I'm sure you'll be much happier.
Your right, it is moving off topic, but let me ask you this - do you actually enjoy wasting 4 or 5 hours (or more) trying to install a program. I understand part of the enjoyment of Slack is that you have to think and do things manually, and I like this part too, but where do you draw the line? This is where I think Slackware has not progressed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.