-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Unable to run executables #3
Comments
The "<executable>" in the command line is supposed to be the actual path of the executable file. In this case, the executable file should be in the build folder and the executable file should be named "ascii_video" As an example to run the program, if executing from the ascii_video-master directory: build/ascii_video -v -c /Users/Sachin/Desktop/Rick Rolls/song240p.mp4 Or alternatively, if executing from the ascii_video-master/build directory ./ascii_video -v -c /Users/Sachin/Desktop/Rick Rolls/song240p.mp4 Thanks very much for the feedback, I'll be sure to make this clearer in the README.md as well by changing it to <path-to-executable> instead of <executable>. Also, please let me know if you find any more problems or have any more suggestions. Hope it works well. |
Thanks for getting back to me so fast! I had it working yesterday but then I did something and now when I run
|
Sorry for the late reply, but I've been digging and testing for a while and I can't really figure out why it would build and then suddenly stop and claim that something "doesn't exist." FFmpeg is really a pain to work with in the first place but I hope it wouldn't just break like that. Do you mind me asking what you mean when you say "I did something"? |
You're going to laugh at this, but when I ran |
Honestly, when I was making this project, it was my first time really working with C and C++ and I didn't really understand concepts like building C software, C libraries (especially FFmpeg’s licensing), and distributing packages for different OS's before diving into the code. That’s mainly the reason why it’s not the easiest to get the program working, so I’m truly sorry about that. Believe me, I’d much rather it be easier as well because it took me quite a while to learn how to build a third party library for the first time, especially when I didn't even get what commands like "cd" and "mkdir" were really doing or what a "current working directory" was. It’s true that the project only depends on FFmpeg and Ncurses, but as far as I know (and correct me if I'm wrong please) there'd still have to be different executables generated for different OS's and architectures, as well as files and keys for package managers and whatnot. While I’m pretty sure this can be done easier with something like VirtualBox, it’s just something that I’m far from familiar with as of now. Basically, it's just something that I haven't touched in or learned as of yet, trying to figure it out as I go. Right now, I'm focusing on trying to clean up the code as it’s quite verbose and difficult to read, and to move the codebase to C++ to depend on C++ 11 std::threads and FTXUI instead of pthreads and Ncurses, so that it can run on non-POSIX operating systems, but I’ll see what I can do about the ease of use for the current release. |
I completely understand. Coding can definitely be tough sometimes, as I've been there myself plenty of times. Please don't feel any pressure to work on this because of me; I am sure there are alternatives. But I do think that you are right in terms of executables, package managers, etc definitely being different depending on the OS, but my guess is that they cannot be too different from each other. Thanks so much for all your help and timely responses! |
I was looking into the errors I was getting, and it is definitely something on my end because it seems like some elements being used were deprecated. I would recommend putting in the |
Hello Coby,
I found your ASCII video player, but I think that I am doing something wrong because I cannot run the executable. I just getting an error saying
zsh: no such file or directory: executable
. I am on a mac if this helps.The text was updated successfully, but these errors were encountered: