Community
Participate
Working Groups
Build Identifier: It seems that autotools doesn't support absolute paths for the configure tool directory option (This is handy on Windows systems, because you can't get relative paths to other drives as far as I'm aware). Simple patch attached, which checks if the path is absolute. If it is, it doesn't append it to the project directory. (Maybe this should be applied to getAutogenPath() as well as getConfigurePath()? Not sure as I've only ever used the latter). Reproducible: Always
Created attachment 184502 [details] Patch to support absolute paths to configure
(In reply to comment #0) > Build Identifier: > > It seems that autotools doesn't support absolute paths for the configure tool > directory option (This is handy on Windows systems, because you can't get > relative paths to other drives as far as I'm aware). > > Simple patch attached, which checks if the path is absolute. If it is, it > doesn't append it to the project directory. > > (Maybe this should be applied to getAutogenPath() as well as > getConfigurePath()? Not sure as I've only ever used the latter). > > > > Reproducible: Always You will need to explain why you need to do this. Why isn't the configure file for the project in the project itself? The patch doesn't address the various other references to srcDir in the file (e.g. autogenPath and passed directly other places)
I often do multiple builds of the same large source tree configured in different ways. (E.g. multiple builds of gcc targeting different architectures/cpu-variants. I'd rather have one source tree on disk, rather than copying 500MB+ for each build). I guess the same patch could be applied to autogen path, but I didn't want touch something I haven't tried and am not familar with.
(In reply to comment #3) > I often do multiple builds of the same large source tree configured in > different ways. (E.g. multiple builds of gcc targeting different > architectures/cpu-variants. I'd rather have one source tree on disk, rather > than copying 500MB+ for each build). > > I guess the same patch could be applied to autogen path, but I didn't want > touch something I haven't tried and am not familar with. This is already possible. You simply add multiple configurations (one per architecture or configuration set-up) using the Manage Configurations button found on the top of the Autotools configure settings page. Each configuration has its own settings, including the Autotools configure settings so you can specify a different --target, etc.... By default, the first build will end up in the top-level directory and every additional configuration will use the configuration name to form a build-directory. So, you can easily keep track of which builds are for what platform by naming your configuration appropriately. See the Autotools User Guide: http://wiki.eclipse.org/Linux_Tools_Project/Autotools/User_Guide and look under the Building section for some further help.
Can we close this one now? Looks like Autotools had support for it.
