Error compiling ART

Ah, my bad. Need to change my default file associations :slight_smile:
Thanks

(Yes! It lives :slight_smile: )

Hi @HIRAM,

that would be great! Let me know if you need a bit more time, I can definitely wait.

Ok. One thing is the bundle identifier will have to be changed from com.rawtherapee to something like com.art
I wonder if com.art is already taken or if you have another suggestion?

I have no idea, but it looks like a very generic name… are there rules to set this bundle identifier? Or can we pick whatever? would art.rawprocessor work?

Well the Apple sorting expectations is the use of R/DNS aka reverse domain name notation. Since the RawTherapee website is rawtherapee.com, it’s bundle identifier is com.rawtherapee
art.com does have an apple app; there is a chance com.art is used by something.

com.art wouldn’t make sense anyway, as that domain is taken already. If the pixls folks don’t mind, we could use us.pixls.art perhaps?

Seems reasonable to me…


Key Property
CFBundleIdentifier (Bundle identifier) The string that identifies your application to the system. This string must be a uniform type identifier (UTI) that contains only alphanumeric ( A - Z , a - z , 0 - 9 ), hyphen ( - ), and period ( . ) characters. The string should also be in reverse-DNS format. For example, if your company’s domain is Ajax.com and you create an application named Hello, you could assign the string com.Ajax.Hello as your application’s bundle identifier.

The bundle identifier is used in validating the application signature.

ping @patdavid @paperdigits any objections?

1 Like

No objection from me.

2 Likes

Furthermore, how about redirecting https://art.pixls.us to https://discuss.pixls.us/tags/c/software/9/art or better yet https://discuss.pixls.us/c/software/art

no problem for me, but I’m not the one who gets to decide… :slight_smile: I’m not sure what the forum policy is regarding this

Fine for me, but then I’d have a request: could you push the new release to a dedicated releases git branch, so that automated packaging can be simplified?

Good job!

yes, definitely!

1 Like

Hello @agriggio
since commit 4a4291d there occurs an error during the compilation process. I filled a issue for 1.0.58 version.
Serge

For those who build on windows, I made a post in ART v1.0 is out about MSYS2/CMAKE crash.
Should be better located here.

Windows build

In Aboutthisbuild.txt, four new items appeared that are empty:
Build OS:
Build date:
Epoch:
UUID:

It’s not annoying but rather intriguing.

they come from a PR about Mac OSX builds. I merged without paying too much attention, and then got some troubles so I had to apply a hotfix. I still need to properly clean up that part.

@agriggio
minor remark: I see no difference between “Build OS:” and “System:”. Perhaps the label “Build OS” is required by Mac OSX build?

my mistake again… build os should be different in case you are cross compiling, but I messed up it seems – I’ll fix it later

@gaaned92 @agriggio
That is my attempt at tracking what and when compiled. It can safely be removed or included for bundle packaging development and bug testing.
See #5648.