../configure does not build make files

[JPRichings]

Hi,

Has the build system been edited since the restructure as i have to run the ./config.status script in build to generate the make files. Is this now the intended behavior?

Regards

James

[aportelli]

We cannot do much for you with so few details, I would need a complete description on how to reproduce the problem. Yes the build system has changed several times recently. However CI systems on various platforms and myself build Grid from scratch using the standard procedure and everything is fine.

Edit: Closed by mistake sorry

[JPRichings]

here is the sequence taken:

1. Clone develop
2. bootstrap
3. configure
4. discover no make file has been created to build against
5. run the ./config.status script to to work out why no make files have been produced.
6. discover the ./config.status script creates the make files.
7. build as normal.

The question is should the ./config.status script be run at the end of the configure script and has it been left off? Does not break functionality just adds an extra step to the build process

[aportelli]

Hi, No this is unnecessary. This is still very vague, the sequence you describe is very generic (bootstrap configure make) and does not encounter any problem at least on Tesseract, the Cambridge system, my machine and all our CI builds. If the configure script did not generate makefiles it probably encountered an error, but I can’t say without any form of log or similar information.

…

On 16 Sep 2018, at 21:24, JPRichings ***@***.***> wrote: here is the sequence taken: Clone develop bootstrap configure discover no make file has been created to build against run the ./config.status script to to work out why no make files have been produced. discover the ./config.status script creates the make files. build as normal. The question is should the ./config.status script be run at the end of the configure script and has it been left off? Does not break functionality just adds an extra step to the build process — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.