|
|
Home » Developing U++ » U++ Developers corner » HelloWorld makefile
|
Re: HelloWorld makefile [message #41304 is a reply to message #41303] |
Thu, 28 November 2013 22:33   |
|
Hi Luigi,
You can try with the universal makefile. Good place to start would be probably something like make -f uppbox/lpbuild2/mkfile PKG=HelloWorld CXX=emcc executed in the checked out svn trunk. Inside the makefile, you can find additional documentation.
I tried to run it of course, but it fails miserably But I haven't even read the instructions, so your results may be better...
I'm really interested in the results, emscripten is very interesting technology. Let us know how it works (or doesn't work). And of course, if you have trouble with the makefile, I can try to help...
Best regards,
Honza
PS: Thinking of it now, is the makefile really necessary? Why not just create emcc build method in TheIDE?
|
|
|
|
|
|
|
Re: HelloWorld makefile [message #41332 is a reply to message #41320] |
Sun, 01 December 2013 12:54   |
 |
forlano
Messages: 1207 Registered: March 2006 Location: Italy
|
Senior Contributor |
|
|
mirek wrote on Sat, 30 November 2013 13:44 |
In the end, we could still have U++/eOS, but as Ctrl::Run is not possible, U++ applications for eOS would have to be specifically altered (quite heavily) to conform with this. E.g. this would not be possible anymore:
if(PromptYesNo("Do you want to perform this operation?")) {
// perform the operation
}
instead, you would need to write
void MyApp::PerformOperation() {
// perform the operation
}
PromptYesNo("Do you want to perform this operation?", THISBACK(PerformOperation))
Mirek
|
Thanks for reply.
I am not sure to have completely understood. But if the problem is only to rewrite the Prompt_like() function of the user application, I am ready for my own app. Perhaps most of us are ready too.
However I am not aware if the whole library needs to be rewritten to accomodate such changes or just a new general function Prompt_eOS() should be added to overcome the issue.
I see huge advantages (both economics (no needs to own Mac & iOS device) and time saved (no new programming language)) that widely compensate the troubbles to rewrite the code of existing apps. Of course for a new app the problem does not exists.
Luigi
[Updated on: Sun, 01 December 2013 12:54] Report message to a moderator
|
|
|
|
Goto Forum:
Current Time: Fri May 09 11:16:45 CEST 2025
Total time taken to generate the page: 0.01240 seconds
|
|
|