Re: TrackerRequestDriver feedback

Hi Petr,

Maybe the built binary should be copied to AppData by make?

I was thinking that only application data (icons, images, …) would be there at first and we’ll leave the application binary in the root dir.

Then the executable should load its stuff from ./AppData which means that we would need the AppData in the same dir as the exe:

install/dir
AppDir (Xml, Images, etx)
calitko

…not a big deal though.

I was actually thinking about this solution when I was reading your reply :). Now it depends on whether there was a problem creating it (I mean dynamically using qmake - simple python script could do that, but it would bring us compilation-time dependancy on python) or when putting there object files.

I’ll give that one a try again! I don’t remember what exactly the problem was but most if not all problems have a cure, so I’m positive about fixing it :-). I’ve created ticket #45 for that, which will have to wait before #44 gets done.

Regards,

Peter

Would you like to post a relpy?


This post is a reply to:
Re: TrackerRequestDriver feedback
Hi Peter, I think I’d call Sources Calitko. Maybe CalitkoMocks better be in . or in ./Utils - the idea is that it eventually becomes a standalone library.Maybe the built binary (more...)

No follow-ups yet.