Skip to content

Missing XEvaluator.cpp file #1

Open

Description

@OscarL

Hello there @Teknomancer! ("BiPolar" here, from the old BeShare days)

There was some comments regarding BeConverter over the Haiku forums, and that prompted me to try to build BeConverter under Haiku beta4 (64 bits).

I've noticed that there seems to be no makefiles/BeIDE projects/etc, so I've added a generic makefile-engine, and started to do minor patches trying to make it build.

But the last error is due to the missing implementation of the things defined in XEvaluator.h. That I can't easily patch :-D

If you ever find the time/will to search again among your backups... it would be nice if you could find the missing pieces!

Thanks in advance! And nice to contact you again after SO many years!

Be well!

PS: this is what I was doing so far, just in case.

Activity

  1. Teknomancer commented on Dec 29, 2022

    @Teknomancer
    Owner

    Hi Oscar (been a long time 😃 👋 )

    I tried searching the backup I had and can't seem to find the missing file.

    Looks like it might need to be re-written. It's a bit of work but should be doable. Just need to fit the evaluator the existing interface in the header or would need some alterations to the users of the interface as well.

    Unfortunately, I don't think I would have time right now to look into this but will try to find some time to do it. My PC at home died so to speak, so working from an older laptop for a few weeks now so don't even have access to my Haiku VM yet (where I used to do some updates on Beezer a year or so ago).

  2. Teknomancer commented on Dec 29, 2022

    @Teknomancer
    Owner

    btw, another thing that's missing are the units themselves. These are files with BFS attributes. They can be re-created once there's something compiling.

    The units cannot be checked into the Git repo directly as we'd lose the BFS attributes, so they would need to be zip'd and commited to the repo. They will have to be unpacked during the build process and cleaned up on make clean stage.

  3. OscarL commented on Dec 29, 2022

    @OscarL
    CollaboratorAuthor

    Thanks a bunch for taking the time to look into this, and for the further details, Ram! No worries regarding time-frames, of course! We Haiku users know to be patient!

    Thanks again. and always know that BeOS/Haiku people loved (and still love) your apps!

  4. Teknomancer commented on Dec 30, 2022

    @Teknomancer
    Owner

    @OscarL I've provided write access for you to this repo, let me know if you didn't get the invite.

  5. OscarL commented on Dec 30, 2022

    @OscarL
    CollaboratorAuthor

    @Teknomancer, got it, thanks!

  6. PeteCA commented on Dec 30, 2022

    @PeteCA

    Hi. Sorry I'm a bit late to the party! Just in case it's not clear, I have all theUnits files -- with Attributes of course. I'll make a zip archive so they can be added here.

  7. Teknomancer commented on Dec 30, 2022

    @Teknomancer
    Owner

    I added a skeleton XEvaluator.cpp in caecddc just to see how it compiles and runs. Ofc, without a function evaluator nothing will actually work but that's the next step.

    Seems to compile fully and the GUI isn't too badly messed up in Haiku. Looks like it will need a bit of work switching to the layout kit etc. but doesn't look unusably bad.

  8. Teknomancer commented on Dec 30, 2022

    @Teknomancer
    Owner

    @OscarL any particular reason the makefile you commited uses ../BeConverter as the app name? The binary file ends up in the Source/ folder. Until the directory structure is sorted out further, maybe we should let the executable be along with the other object files in objects.<xyz>?

  9. PeteCA commented on Dec 30, 2022

    @PeteCA
  10. OscarL commented on Dec 31, 2022

    @OscarL
    CollaboratorAuthor

    @Teknomancer:

    any particular reason the makefile you commited uses ../BeConverter as the app name

    Just because it was more convenient from a HaikuPorter's recipe point of view. That way the binary ends ups in a "known location" (as the name of the object folder changes depending on which compiler we're using when building the recipe: 64 vs 32 bits, GCC2 vs newer GCC11).

    That way, the "recipe" can just copy it from there to the install location after calling make, and create the .hpkg afterwards.

    No other particular reason. There might be a better way, I'm stll a newb regarding build systems and HaikuPorts recipes, so feel free to change as you think it's best.

  11. Teknomancer commented on Dec 31, 2022

    @Teknomancer
    Owner

    Heh... You beat me to it! That was going to be my project for today... I figured I could do that quickly and would be a useful check. Glad to know it compiles. Thanks!

    Ah, sorry wasn't aware you were planning to work on it.

    @Teknomancer:

    any particular reason the makefile you commited uses ../BeConverter as the app name

    Just because it was more convenient from a HaikuPorter's recipe point of view. That way the binary ends ups in a "known location" (as the name of the object folder changes depending on which compiler we're using when building the recipe: 64 vs 32 bits, GCC2 vs newer GCC11).

    That way, the "recipe" can just copy it from there to the install location after calling make, and create the .hpkg afterwards.

    No other particular reason. There might be a better way, I'm stll a newb regarding build systems and HaikuPorts recipes, so feel free to change as you think it's best.

    Okay, I tried playing with OBJ_DIR, OBJDIR in the Makefile but to no effect, but I'll worry about this later. For now, it can probably be the way it is but should be changed to a defined, statically named location in the future (to help with Haikuports/recipe). It also helps with adding it to .gitignore as well.

  12. self-assigned this
    on Dec 31, 2022
  13. PeteCA commented on Dec 31, 2022

    @PeteCA
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions