Community
Participate
Working Groups
It would be great if we automatically upload sdm. If the binary version would come with sdm compiled for linux x32/x64/ppc + aix/ppc then one would cover >95% of systems (using top500 as reference). Also dependencies wouldn't be a problem if it is compiled against glibc <=2.3. I would assume that build.eclipse.org has a cross compile installed, thus compiling these as part of the head-less build shouldn't be difficult
(In reply to comment #4 of 316079) > Open a bug on it. It's a bit of a logistical headache, and we'd need volunteers > to maintain the different platforms, but worth thinking about. We used to > distribute proxy binaries, but that was a nightmare due to different API and > O/S version combinations. The SDM doesn't use anything except standard O/S > interfaces, so it should be relatively more portable. You don't think it is possible to cross-compile it for all platforms on the eclipse build server? As you said, sdm doesn't have any dependencies and thus cross-compiling it should be rather straight forward. And I was assuming that they have the cross-compilers installed to compile SWT.
Committed to master. There are now three fragments containing pre-compiled sdm executables for the following architectures: aix/ppc64, macosx/x86_64, linux/ppc64, and linux/x86_64. These are compiled by hand and committed to the git repo. Since they only change when the sdm source is modified this is not too onerous. Prior to launching the debugger, the target os and architecture is checked and if there is a match, the corresponding executable uploaded (if not already available). If there is no match or the option is disabled, the debugger falls back to the path specified in the launch configuration.
Closing as resolved.
(In reply to comment #2) > Committed to master. > > There are now three fragments containing pre-compiled sdm executables for > the following architectures: aix/ppc64, macosx/x86_64, linux/ppc64, and > linux/x86_64. These are compiled by hand and committed to the git repo. > Since they only change when the sdm source is modified this is not too > onerous. Hi Greg, just checking: did you compile it with glibc <= 2.3? > > Prior to launching the debugger, the target os and architecture is checked > and if there is a match, the corresponding executable uploaded (if not > already available). If there is no match or the option is disabled, the > debugger falls back to the path specified in the launch configuration.
