Package Base Details: amdapp-sdk

Git Clone URL: https://aur.archlinux.org/amdapp-sdk.git (read-only, click to copy)
Submitter: Vi0L0
Maintainer: rigred
Last Packager: satcom886
Votes: 83
Popularity: 0.000022
First Submitted: 2013-02-11 21:03
Last Updated: 2019-08-16 21:33

BluePeril commented on 2010-12-29 08:05

The checksum of the 32bit version is wrong. It should be 07fd15a51a678c4378767f61466daf9da21d0bab6088a97a70136dd8c976aca6

kralyk commented on 2010-12-28 21:20

Meh, thanks, fixed...

schneida commented on 2010-12-28 20:52

Sry, but the download for the source file is wrong. It downloads the license agreement instead of the actual file. A correct url would be: http://download2-developer.amd.com/amd/Stream20GA/ati-stream-sdk-v2.3-lnx32.tgz

kralyk commented on 2010-12-28 16:02

Updated.
Pkg doesn't include the header now and has been cleaned & simplified.

big_gie commented on 2010-12-17 18:12

You were too fast, yes I agree that this package should remove the headers ;)

big_gie commented on 2010-12-17 18:11

All headers are, I think, almost the same, you can verify by yourself.
I think the best generic approach would be to let opencl-headers install the headers and remove the headers from these packages.

Anonymous comment on 2010-12-17 18:11

Or perhaps the "Arch Way" would be to not include the headers in this package, and point users to the "opencl-headers" package if they need them?

Anonymous comment on 2010-12-17 18:07

Would it be possible to add "opencl-headers" to the "provides" array, so that a user with this package installed may build packages that makedepend on "opencl-headers", or are the headers from this package too dissimilar to those from "opencl-headers"?

Anonymous comment on 2010-12-06 14:45

I am a robot. This is not an official message. AUR guidelines suggest to not include binaries. Examples:
amdstream/more-docs.tar.gz
Feel free to disregard this as you would any other comment. This robot will not post here again.

kralyk commented on 2010-09-04 10:41

Can you please provide wich package those files belong to? So I can put it in conflicts.