|
|
Subscribe / Log in / New account

Zimmerman: We’ve packaged all of the free software…what now?

Zimmerman: We’ve packaged all of the free software…what now?

Posted Jul 8, 2010 11:13 UTC (Thu) by nlucas (guest, #33793)
In reply to: Zimmerman: We’ve packaged all of the free software…what now? by mjthayer
Parent article: Zimmerman: We’ve packaged all of the free software…what now?

Well, one thing I agree. Shipping binaries it's the easy part.


to post comments

Zimmerman: We’ve packaged all of the free software…what now?

Posted Jul 8, 2010 11:23 UTC (Thu) by mjthayer (guest, #39183) [Link] (6 responses)

> Well, one thing I agree. Shipping binaries it's the easy part.

When I said "shipping", I included building and solving binary compatiblilty issues in that. It really isn't too hard - build on the oldest system you want to support, decide what dependencies you can rely on the system to provide and ship the rest static, load a couple of things at runtime if in doubt. There are still a couple of gotchas (the autopackage web page has good information on the subject, although C++ ABIs are no longer a problem, and glibc is getting better at not pulling in new features unless you actually use them), but it is still quite feasible. And once you have solved the problems, they stay solved on the whole.

Zimmerman: We’ve packaged all of the free software…what now?

Posted Jul 8, 2010 11:31 UTC (Thu) by nlucas (guest, #33793) [Link] (2 responses)

Right. That's exactly what I was agreeing to.
And the current C++ ABI stability plays a big part in that, contrary to the hell it was earlier (and worst on Windows because there were more than one mainstream compiler).

Zimmerman: We’ve packaged all of the free software…what now?

Posted Jul 8, 2010 11:35 UTC (Thu) by mjthayer (guest, #39183) [Link] (1 responses)

> And the current C++ ABI stability plays a big part in that, contrary to the hell it was earlier (and worst on Windows because there were more than one mainstream compiler).

I thought that Windows people used COM for ABI because it is well defined.

Zimmerman: We’ve packaged all of the free software…what now?

Posted Jul 8, 2010 15:25 UTC (Thu) by nlucas (guest, #33793) [Link]

COM has nothing to do with C++ objects, although there are Microsoft C++ extensions to the language to make it easy to work with it inside C++.
You can use COM in a pure C program.

Zimmerman: We’ve packaged all of the free software…what now?

Posted Jul 8, 2010 15:18 UTC (Thu) by foom (subscriber, #14868) [Link] (2 responses)

> although C++ ABIs are no longer a problem

Hm. Unfortunately, I think they will be again at some point soon. It sounds like when G++'s C++0x support is finalized, they're going to have to change the ABI of std::string and maybe a few other core classes. (okay, so, that's not a C++ ABI break, only an STL ABI change).

Zimmerman: We’ve packaged all of the free software…what now?

Posted Jul 12, 2010 13:25 UTC (Mon) by HelloWorld (guest, #56129) [Link] (1 responses)

Do you have any reliable sources that state this?

Zimmerman: We’ve packaged all of the free software…what now?

Posted Jul 15, 2010 14:51 UTC (Thu) by nix (subscriber, #2304) [Link]

There have been discussions to this effect on the GCC mailing list. It's not unsubstantiated scuttlebutt. (Perhaps a way will yet be found to avoid a std::string ABI change, but none is yet evident.)


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds