Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Matlab interface is broken #10889

Closed
abuts opened this issue Aug 4, 2014 · 3 comments
Closed

Matlab interface is broken #10889

abuts opened this issue Aug 4, 2014 · 3 comments
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@abuts
Copy link
Member

abuts commented Aug 4, 2014

This issue was originally TRAC 10047

The changes made for ticket http://trac.mantidproject.org/mantid/ticket/9731 broke Matlab Interface.

@abuts
Copy link
Member Author

abuts commented Dec 8, 2014

@abuts (2014-10-01T15:26:16):
refs http://trac.mantidproject.org/mantid/ticket/10047 Add to cmake option of not building the Matlab interface

by default until matlab interface is fixed.

21aeb05


@abuts (2014-10-01T15:50:00):
refs http://trac.mantidproject.org/mantid/ticket/10047 Correct way of adding matlab option

89fdb52


@abuts (2014-10-01T15:57:55):
I've merged this change to master as apparently nobody except myself is using/having Matlab, so it should affect only myself and it is highly annoying to have every nightly build broken on my local machine.

When the bug is properly fixed, It is pretty easy to remove this change.


@martyngigg (2014-10-02T07:36:26):
This should not have been merged directly to master without at least checking with someone else first. It would have been a simple matter to add another ticket about having an option to build matlab & ask someone else to look at it. I don't see why the system had to be subverted here?


@abuts (2014-10-02T08:17:12):
Replying to [comment:5 Martyn Gigg]:

Only because the changes are trivial and irrelevant to the majority and I want the builds to be clean for tomorrow when usual way of doing things would last 24hrs+


@NickDraper (2014-12-08T10:25:36):
Moved to the backlog at the code freeze of R3.3

@abuts abuts added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@stale
Copy link

stale bot commented Feb 23, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 23, 2021
@martyngigg
Copy link
Member

The matlab interface no longer exists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

3 participants