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.

Sign up for GitHub

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

Jump to bottom

Error messages on startup #4017

Closed
martyngigg opened this issue Jun 10, 2011 · 1 comment
Closed

Error messages on startup #4017

martyngigg opened this issue Jun 10, 2011 · 1 comment
Assignees
@martyngigg
Milestone
Iteration 29

Comments

@martyngigg
Copy link
Member 

Welcome to Mantid - Manipulation and Analysis Toolkit for Instrument Data
Could not open library C:\MantidProject\builds\trunk\bin\Debug\\Lib.dll: failed with error 126: The specified module could not be found.


Error opening C:\MantidProject\builds\trunk\bin\Debug\Lib.
Could not open library C:\MantidProject\builds\trunk\bin\Debug\\Lib.dll: failed with error 126: The specified module could not be found.


Error opening C:\MantidProject\builds\trunk\bin\Debug\Lib.
Could not open library C:\MantidProject\builds\trunk\bin\Debug\\Lib.dll: failed with error 126: The specified module could not be found.


Error opening C:\MantidProject\builds\trunk\bin\Debug\Lib.

Since the python bundling on Windows, when you start Mantid with the plugins directory pointed at bin you get these messages.
@martyngigg
Copy link
Member Author

This issue was originally trac ticket 3170

@martyngigg martyngigg self-assigned this Jun 3, 2015
@martyngigg martyngigg added this to the Iteration 29 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martyngigg martyngigg

Labels
None yet
Projects
None yet
Milestone
Iteration 29
Development

No branches or pull requests
1 participant
@martyngigg