* sim/common/version.in?
@ 2009-10-05 16:07 Doug Evans
2009-10-05 17:23 ` sim/common/version.in? Joel Brobecker
0 siblings, 1 reply; 2+ messages in thread
From: Doug Evans @ 2009-10-05 16:07 UTC (permalink / raw)
To: gdb
Hi.
IWBN if one could build a simulator in src/sim without requiring
the gdb sources in src/gdb.
This is doable today (for the sim I tried, m32r) with one nit:
src/gdb/version.in.
A cronjob could periodically update src/sim/common/version.in from
src/gdb/version.in, for example.
That would still leave updating the file for releases,
but if there was a script that was run to help prep a release,
it could also copy src/gdb/version.in to src/sim/common/version.in.
I'm fine with things being the way they are, but the topic has
come up, so I'm pinging the community for opinions.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: sim/common/version.in?
2009-10-05 16:07 sim/common/version.in? Doug Evans
@ 2009-10-05 17:23 ` Joel Brobecker
0 siblings, 0 replies; 2+ messages in thread
From: Joel Brobecker @ 2009-10-05 17:23 UTC (permalink / raw)
To: Doug Evans; +Cc: gdb
> A cronjob could periodically update src/sim/common/version.in from
> src/gdb/version.in, for example. That would still leave updating the
> file for releases, but if there was a script that was run to help prep
> a release, it could also copy src/gdb/version.in to
> src/sim/common/version.in.
The release process is a collection of scripts, so adding that extra
step would mean updating the scripts once.
I'm also fine either way. Gdbserver is in the same situation; it can be
configured independently of GDB, but still needs access to the GDB sources.
--
Joel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-10-05 17:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-10-05 16:07 sim/common/version.in? Doug Evans
2009-10-05 17:23 ` sim/common/version.in? Joel Brobecker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox