On Tue, 2014-09-30 at 18:23 -0400, Peter Foley wrote:
On Tue, Sep 30, 2014 at 8:00 PM, David Ostrovsky d.ostrov...@gmx.de wrote:
Yes, i can reproduce that. The reason is Win32 make. It confuses some of
regex in gbuild-to-ide generator. Peter Foley mentioned in another
thread that he is
At Wed Sep 10 03:16:02 PDT 2014, Juergen Funk wrote:
I have make the build in the core and build all of them, the last
command look like okay, but the solution in the lo-core directory
has the follow entry
Microsoft Visual Studio Solution File, Format Version 12.00
[...]
Yes, i can
On Tue, Sep 30, 2014 at 8:00 PM, David Ostrovsky d.ostrov...@gmx.de wrote:
Yes, i can reproduce that. The reason is Win32 make. It confuses some of
regex in gbuild-to-ide generator. Peter Foley mentioned in another
thread that he is going to increase GNU make version to 4.0 to run
Hi,
welcome onboard Juergen!
On Wed, Sep 10, 2014 at 10:16:02AM +, Juergen Funk wrote:
Now my problem at the moment is to try do build the VS solution but
I get follow
Hmmm, I dont know much about how MSVS solution files should look like.
But as a starting point I can hint you at the
On Wed, Sep 10, 2014 at 11:11:13AM +, Juergen Funk wrote:
I'm not sure where is the fault is that make (have no plan too) or
is that the python script.
Does a running make alone lead to a successful build? Can you run the product
after the build?
Note the MSVS integration needs one
On Wed, Sep 10, 2014 at 12:00:13PM +, Juergen Funk wrote:
Yes it is running, in this case all is fine.
So, if the MSVS solution generation still doesnt work after that, the:
make[1]: ***. Stop.
Suggests that the:
LC_MESSAGES=C D:/Dev/cygwin/opt/lo/bin/make
