If I compile one of the projects lying in the codebase, say nuspell, and it
produces new files, say exe/lib/dll, are these files automatically added to
the codebase when I do a commit and push? Ir do I have to manually add them?
OK.I got hunspell-1.3.3 to compile, on Windows using MSYS2 and WinGW64.
Nuspell is still a little down the road but the're so similar that there
shouldn't be any real difference, I'll start with hunspell and make nuspell
work down the line,
This also solves my problem if changes would be automagically included or
not. It's another install.
But I'm about to rewrite this DLL. With Pete's advice it should be fairly
simple. I'll find the typedefs or #defines later. As long as I know what
they're suppposed to be I should be OK.
If I compile one of the projects lying in the codebase, say nuspell, and it
produces new files, say exe/lib/dll, are these files automatically added to
the codebase when I do a commit and push? Ir do I have to manually add
them?
If I compile one of the projects lying in the codebase, say nuspell, and it
produces new files, say exe/lib/dll, are these files automatically added to
the codebase when I do a commit and push? Ir do I have to manually add them?
Regards.
OK.I got hunspell-1.3.3 to compile, on Windows using MSYS2 and WinGW64.
Nuspell is still a little down the road but the're so similar that there
shouldn't be any real difference, I'll start with hunspell and make nuspell
work down the line,
This also solves my problem if changes would be automagically included or
not. It's another install.
But I'm about to rewrite this DLL. With Pete's advice it should be fairly
simple. I'll find the typedefs or #defines later. As long as I know what
they're suppposed to be I should be OK.
Regards,
On Tue, Oct 9, 2018 at 6:17 PM Soren Bro sbrothy@users.sourceforge.net
wrote:
Sorry for taking so long to answer this. I believe you have to add them manually.