iOS Static Libraries Are, Like, Really Bad

Re:iOS Static Libraries Are, Like, Really Bad by mwcampbell on Sunday January 12, 2014 @04:52PM (#7047597)

I wish that embedding resources in programs as const byte arrays were more common. I think that approach leads to a tightly integrated, low-overhead app, especially on platforms (not iOS) where users and third-party programs are free to do stupid things with the file system; the app either works completely or isn't there at all.

[ Parent | on HN ]

Re:iOS Static Libraries Are, Like, Really Bad by liuliu on Sunday January 12, 2014 @05:39PM (#7047790)

You mean like: https://github.com/liuliu/mopack? But unable to inspect the embedded resource at programming time is a big show-stopper for me.

[ Parent | on HN ]

Re:iOS Static Libraries Are, Like, Really Bad by frou_dh on Monday January 13, 2014 @04:49AM (#7049686)

    $ xxd -i some_file

[ Parent | on HN ]

Re:iOS Static Libraries Are, Like, Really Bad by liuliu on Monday January 13, 2014 @01:47PM (#7052492)

last time I checked, Microsoft has a weird restriction on their c++ compiler (they don't have a c compiler) that only allows 4k length const chars, you have to concatenate consts to get arbitrary length.

[ Parent | on HN ]

Re:iOS Static Libraries Are, Like, Really Bad by gte910h on Sunday January 12, 2014 @05:08PM (#7047658)

I agree bundles are a pain in the ass. This is a bit overboard for some libraries and can have unforeseen memory issues

[ Parent | on HN ]

Re:iOS Static Libraries Are, Like, Really Bad by mwcampbell on Sunday January 12, 2014 @05:10PM (#7047668)

What memory issues? const data can be mapped and unmapped on demand.

[ Parent | on HN ]