From: "Johannes Schindelin" <Johannes.Schindelin@xxxxxx>
Hi Philip,
On Thu, 20 Nov 2014, Philip Oakley wrote:
[...]
+Or, use the msvc-build script; also in /msysgit/bin/msvc-build
As I mentioned before, from a Git Bash on Windows, the path is
/bin/msvc-build (no /msysgit/). That is quite likely to stay the same
with
the upcoming Git for Windows SDK, too (once I add the file to the
SDK).
I was trying to identify the source file (as I see it in my Msysgit
install). However it will all need tidying to distinguish what is seen
if you have G4W-SDK, rather just installing the new G4W (when ready)
By the way, I think we should also start thinking about a Jenkins job
to
verify that upstream changes such as invalidcontinue.obj do not break
the
MSVC build. Please let me know if you want to give it a try, I have a
Windows Azure instance with a Jenkins instance, sponsored by
Microsoft.
This is not something I'm familiar with, but it's something I could have
a look at.
On my list is also the 'git bundle' symref problem, which we've got a
solution for that 'just' needs coding, along with thoughts about
narrow/sparse checkout/clone/fetch.
One of the confusions I have is the distinction between building with
the MSVC compiler (cl command line) and building within VS2008, and
whether they are different things (i.e. does VS2008 bring extra
baggage?).
--
Philip
Ciao,
Johannes
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html