Discussion Overview
The discussion revolves around compiling a MATLAB GUI interface that utilizes MEX files into a standalone application. Participants explore issues related to the compatibility of the compiler with MEX files and the potential need for alternative approaches to hardware control.
Discussion Character
- Technical explanation
- Debate/contested
Main Points Raised
- One participant reports an error when attempting to compile a GUI interface with MEX files using the deploytool's build function.
- Another participant questions the choice of compiler and suggests that MATLAB's internal compiler may not support MEX files, recommending the installation of MCD for recompilation.
- A participant clarifies that they are using the Lcc-win32 C 2.4.1 compiler and expresses uncertainty about whether it is MATLAB's internal compiler, noting that they can compile simple .m files without issue.
- One participant proposes that the user might need to write two separate programs: one for hardware control and another for post-processing, suggesting a potential workaround for the MEX file issue.
- A later reply confirms that the problem persists across different compilers, indicating that the issue is indeed related to the MEX files.
Areas of Agreement / Disagreement
Participants generally agree that the issue is related to the MEX files and their compatibility with the chosen compiler. However, there is no consensus on the best approach to resolve the problem, with differing opinions on whether to separate the programs or find a compatible compiler.
Contextual Notes
The discussion highlights limitations regarding the compatibility of various compilers with MEX files and the specific requirements of the hardware being controlled, which may affect the proposed solutions.
