V103 – bloody annoyed!

About Monkey 2 Forums Monkey 2 Development V103 – bloody annoyed!

This topic contains 10 replies, has 5 voices, and was last updated by  cocon 2 years, 8 months ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #3000

    AdamStrange
    Participant

    There I’ve said it.

    MARK… YOU BROKE THE BLOODY SHIP!

    major becomes a reality, that has become my nightmare. because the nice Ted21 editor no longer compiles, functions, etc.

    I now have to work out how the complete mess can be worked around. Way to go…

    #3001

    Mark Sibly
    Keymaster

    MARK… YOU BROKE THE BLOODY SHIP!

    I have tried to make clear in the past that hidden APIs are hidden for a reason, and that mojox was still under active development (which is why it was rolled into Ted2 and not a standalone module) but apparently I didn’t try hard enough. Please keep this in mind for the future – if you use any ‘hidden’ or other experimental stuff that’s not docced, you run the risk of it getting ripped out or changed at a later date.

    But what problems are you having anyway? If you’re using your own fork of the old mojox, it should be relatively easy to get going as nothing major has really changed in mojo – perhaps the names of a few internal methods (many of which will now be public), but that should be about it.

    #3014

    cocon
    Participant

    Perhaps Adam made a few additions into mojox, if I remember correctly by looking at his repo. Adam, you might try to keep a separate fork of mojox since it will become a standalone project later on, you would control the changes of the libraries that way (ted21-mojox-other).

    #3016

    degac
    Participant

    Ok

    1. I download and installed MX2 v103.
    2. Copied the ‘devtools’ (from MX2 v100) into the new one.
    3. Launched the rebuildall.bat

    I did point 3 many times… too many! 😀

    At the end I found the ‘ted2’ v.2 (the new one), mx2cc reports v.1.0.3… but once I try to compile everything (in this case the hello-world.monkey2 example) I get a mountain of errors!

    What’s wrong???

    #3030

    Mark Sibly
    Keymaster

    Definitely looks like a mingw version mismatch error, which theoretically shouldn’t happen if you’ve got the correct mingw in devtools.

    Perhaps try removing any another mingws you have from your system PATH?

    #3069

    AdamStrange
    Participant

    ok, so I’m now refactoring all the code to make it unique.

    As far as I was aware I wasn’t using any ‘hidden’ api’s, but take the point about mojox. I’ll need to refactor this as well

    #3079

    AdamStrange
    Participant

    Mark:

    how do Resolve the changes you’ve made to mojo/view and  mojo/style? Basically preventing any ted21 stuff compiling.

    Whilst moving mojox into a module is (in some terms) a good idea. It was not particularly transparent to developers.

    I do feel that in the move you have taken something that was difficult and now made it substantially more difficult to find out what it does and how to extend it.

    I would really have thought that doing this would make things more transparent, not less?

    How do you suggest I continue from here?

    I really wanted this to all work well together and be something everyone could benefit from.

    #3081

    degac
    Participant

    @Mark

     

    I will try to remove any other refer to MinGW in path, BUT as I’m using Bmax I suspect it will break things somewhere 🙂

    About Ted2:

    It would be useful some ‘info’ report:

    • mx2cc version
    • Ted2 version
    • MinGW version / path

    etc

    Just to know what user is using.

    Another question: maybe I’m wrong, but I remember you are thinking about some info about ‘internal version’ for each modules. Is still a valid thing or not?

    In this way (refering to AdamStrange) anyone could use a ‘determinated’ version of that module (ie:mojox.101 when the latest one is mojox.103)
    No idea how to implement it in the parser/compiler!

    #3085

    Chapman7
    Participant

    Adam you should have known MojoX was in heavy development (I did)… it wasn’t even an actual module until v103. He isn’t going to to support backwards compatibility for something that’s not even finished so I am really not sure why you keep bringing it up (On this and other forums…) I understand you are frustrated but your best course of action is to update the new Ted2 or go through all of the changes made, and update your code to match it.

    #3095

    degac
    Participant

    Found the problem: a (damned!) typo in the env_windows.txt file for the MINGW path (!)
    Now everything is working (no need to change other MINGW parameters around).

     

    about the idea of different version (of a module):

    it would be possible (of course this means a *little* rewriting of the tools …) having – for each module – a subdir (like 100) that represents a specific version.

    If there’s no the required version, the compiler uses the current one (ie: 103) otherwise what needed from the user.

    The main advantage is that the ‘first’ level of the module structure (emscripten, freetype, gles20 ecc) is like the actual one, only internally could be different version available.
    Sure there is the risk of duplication in files.

    Moreover ‘beta’ version could just be downloaded & installed in the ‘current’ MX2 folder (unless – of course of big changes in mx2 itself).

    #3103

    cocon
    Participant

    I have MinGW extracted in “D:\Programs\monkey2mingw\mingw32\bin\g++.exe” and I have deleted the “devtools” folder, and created a “devtools” folder link instead (a junction, with the program SymLinkCreator). Actually I did not know about “evn_window.txt”, perhaps I might try to use it from now on.

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.